-
Notifications
You must be signed in to change notification settings - Fork 26.1k
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
% in url parameter causes "Uncaught URIError: URI malformed" #12145
Comments
Hello, |
Hi, I have a similar problem, but I am trying to put a percent sign value on a URL segment as some id for dynamic routing. Regardless of whether I am encoding a percent sign or not. If I pass it to router.push in "asPath" as part of the segment URL the same error (URIError: URI malformed) occurs. |
Hi, this has been updated in the latest version of Next.js Example deployment can be seen here https://test-malformed.vercel.app/dynamic/first?utm_content=Lookalike%201%2520-%20Ages%2035-54%20-%20USA_Product%20Focus%20-%20Conversion%20-%20Laptop%20V1_23844117712240465 |
This closed issue has been automatically locked because it had no new activity for a month. If you are running into a similar issue, please create a new issue with the steps to reproduce. Thank you. |
Bug report
Hitting a next.js site with a query string parameter containing a percent sign causes consumer to experience a plain white screen.
To Reproduce
Hit a next.js site with a query parameter containing a percent sign:
https://vercel.com/?q=%
Expected behavior
Page still renders fine and perhaps console logs that a query parameter had a URI malformed issue.
Full Error
System information
Additional context
Content is currently coming in with a raw percent on utm_content and that is out of my immediate control to change:
The URLs are auto generated by facebook ads manager. I guess they are not properly encoding their utm_content value? If I decode the value to
Lookalike 1% - Ages 35-54 - USA_Product Focus - Conversion - Laptop V1_23844117712240465
and re-encode, it works.(somewhat related issue #10080)
The text was updated successfully, but these errors were encountered: