: Usage of special characters in the URL path instead of query-strings to allow relative linking in a web proxy I've received complaints that the links that my software is generating aren't following
I've received complaints that the links that my software is generating aren't following the W3C URL-specification. www.w3.org/Addressing/URL/url-spec.txt
The links generated looks like this: organization.proxive.se/proxive/https://www.google.com/
The software is a proxy and generates the links this way so that the proxy doesn't have to parse relative links. Examples: /maps/, ../relative_link.
Using a solution that uses query-string wouldn't allow this.
Is my usage correct of constructing the URL correct or should I URL encode everything after /proxive/?
I can add that my solution works in all major browsers.
More posts by @Lee4591628
1 Comments
Sorted by latest first Latest Oldest Best
It appears that the only thing that you would need to escape in that URL would be the :
organization.proxive.se/proxive/https%3A//www.google.com/
Then your URL wouldn't use any disallowed characters and the directories would still be on the sub URL for supporting some relative links.
I just want to point out that not all relative links will work. I usually code my sites to work with site relative URLs like /img/logo.png When used on example.com/dir/page.html it will fetch the relative URL example.com/img/logo.png.
So in your case if you tried to proxy example.com/dir/page.html it would end up fetching organization.proxive.se/img/logo.png
Terms of Use Create Support ticket Your support tickets Stock Market News! © vmapp.org2024 All Rights reserved.