Include client's User-Agent header in requests to NextJS server from NextJSProxyView #33
Conversation
This file contains 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
|
Thank you for your contribution! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This includes the end user's
User-Agentheader value in requests to the NextJS server from theNextJSProxyViewdevelopment proxy.We ran into an issue with using
req.headers['user-agent']ingetServerSidePropsto vary API calls between desktop and mobile clients. TheUser-Agentvalue was from the Django server,Python-urllib/3.8. (Note that our issue appears fixed after converting from the Pages Router to the App Router, but this could be useful for apps that have not yet converted to App Router.)