Also If … For example, forward slash characters are used to separate different parts of a URL (or more generally, a URI).
Using percent-encoding, reserved characters are represented using special character sequences.
I need to pass a parameter string that contains slashes to a REST call. ok ok, Your answer got me thinking and I finally was able to resolve this.
Unreserved characters have no such meanings.
An attacker could submit /www.google.com as a URL, and code that only adds a forward slash might unwittingly enable an external redirect. Thus, it would look like this: Does anyone have any help or insight? This route will no longer be triggered for that URL. But also if you use HttpWebRequest you can actually tell not to encode the URL, either way it should work. I broke the URL up into 4 seperate Parameters so there was no slash (/) in any value and then I placed the final data portion of the URL (20151103^960^960^103694) in it's own parameter.
The double slash redirect does not work in Visualforce at this time, so to demo this we have included the onCancel URL parameter and a Cancel button, which uses a JavaScript-based redirect rather than the Apex PageReference() method. I think the culprit is c2d7ae4, which started URL decoding the URI. Is there a way to encode just the data part of the url so that it does not force encoding the rest of the url? ? c# - net - forward slash in url parameter . GETting a URL with an url ... GET {url}/{url-encoding of base-64 encoding of the DER encoding of the OCSPRequest} I am very open to other readings of this, but I cannot see what else could be meant. Using percent-encoding, reserved characters are represented using special character sequences.
I tried URL encoding, or making URL map to accept query parameter instead of path parameter but apparently we only allow for path parameters. For example, forward slash characters are used to separate different parts of a URL (or more generally, a URI).
After upgrading from 3.7.0 to 3.8.0, routes that contain a url encoded forward slash no longer work. Unreserved characters have no such meanings. Example route: /auth/{code} Example url: /auth/4%2FGtXcKpxJQk97MyRtHOy_6sPKrLz74-nDkKG6-iz-PIc. No resolution on this yet.
Double encode it : %252F. As Scru said, if you're trying to pass the values as a GET, you need to URLencode the string containing the date. If you feel some overwhelming need to do this manually, the URL encoding for a forward slash is '%2F'.