fix: use req.originalUrl for correct path extraction in NestJS#178
Merged
HugoRCD merged 2 commits intoHugoRCD:mainfrom Mar 14, 2026
Merged
fix: use req.originalUrl for correct path extraction in NestJS#178HugoRCD merged 2 commits intoHugoRCD:mainfrom
req.originalUrl for correct path extraction in NestJS#178HugoRCD merged 2 commits intoHugoRCD:mainfrom
Conversation
|
@ruisaraiva19 is attempting to deploy a commit to the HRCD Projects Team on Vercel. A member of the Team first needs to authorize it. |
Contributor
|
Thank you for following the naming conventions! 🙏 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
🔗 Linked issue
📚 Description
req.urlcan be changed by other middleware (e.g. global prefix, proxy). Using Express’sreq.originalUrlkeeps the path as it was when the request hit the app, so logs show the real route.📝 Checklist