paths with query get escaped
See original GitHub issueHi, i use a generated image containing query parameters as og image, but the path in the final output include escaped &
making the path invalid:
path:
https://images.ctfassets.net/gz0sygvqczyz/1LlU2yNbXooedOqW3UeNA1/b1d427094354ac34cf9dc4f8a319957a/fieldset.png?fit=pad&f=top&w=1200&h=630&bg=rgb:F3F6F9
output:
https://images.ctfassets.net/gz0sygvqczyz/1LlU2yNbXooedOqW3UeNA1/b1d427094354ac34cf9dc4f8a319957a/fieldset.png?fit=pad&f=top&w=1200&h=630&bg=rgb:F3F6F9
The original path is working, while the second one nope, causing a wrong parsing by crawlers.
Issue Analytics
- State:
- Created 4 years ago
- Reactions:1
- Comments:5 (1 by maintainers)
Top Results From Across the Web
How to automatically escape item paths for use in Sitecore query
I am building a query string in code which uses an item path. If the item path contains a hyphen or underscore, then...
Read more >What characters must be escaped in an HTTP query string?
The answer lies in the RFC 3986 document, specifically Section 3.4. The query component is indicated by the first question mark ("?
Read more >path should also be escaped · Issue #25 · elm/url - GitHub
I will say that it DOES escape query parameters... but if you are building an API url for example and some parameters are...
Read more >Spaces in URL file path (as opposed to query string) are ...
Spaces in URL that are before a query parameter should be escaped as %20 during a copy/paste operation, rather than a + symbol....
Read more >HttpRequest.get_full_path does not escape # sign in the url
request.get_full_path() returns the path with the query string (if there is one). The result doesn't have any particular encoding or escaping applied.
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Hey @equinusocio, really sorry I only got some time now to really look into this. After doing some digging it seems like this is an issue in React itself. I don’t think there is anything I can on this end.
@garmeeh I had to switch to Nuxt because this issue. vue-head for example has a
__dangerouslyDisableSanitizers
to disable string encoding inside all meta or__dangerouslyDisableSanitizersByTagID
to disable encoding on specific elements.