-
Notifications
You must be signed in to change notification settings - Fork 2.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
encoded character in url causes "Initial URL does not match URL at time of hydration" #8872
Comments
Hm, maybe we need to be decoding these before the comparison?
I'm slightly surprised the server Request url and browser URL differ on the comma - might need to dig into why those are behaving differently |
I'm also curious if this behaves the same on an Express server, or if this is something specific to how AWS lambda encodes URLs |
came here to post this. took a look at my analyics today and saw someone was visiting hoping this one is fixed soon! e: i'm using the default remix server running on a linux VPS, fwiw, so i don't think it's an AWS thing |
This should be resolved via #9695 and available in the next release 👍 |
🤖 Hello there, We just published version Thanks! |
confirmed good on 2.11.0, thanks! |
🤖 Hello there, We just published version Thanks! |
Reproduction
https://github.com/WillSmithTE/grunge-test-2
https://19przkzqw9.execute-api.us-west-2.amazonaws.com
This is deployed with the grunge stack on lambda, and the whistler blog title (and url) has an encoded character, "," (or "%2C")
in the html, this is the remix context, note the "decoded" comma
Used Package Manager
npm
Expected Behavior
Page loads normally
Actual Behavior
Page infinitely refreshes cause of the mismatch between encoded and decoded comma
The text was updated successfully, but these errors were encountered: