Uri and the %2f and %5c escape codes.

[Paul Linville]

We need to be able to use the following URL that is given to us by a test
harness.

hTTps://000.000.000.000:000/59B9F4F...~CYRe.H.$%4CMp%CBCr'xm!y%D3HW%F2%5D+7@JvR%B7Z


I cannot construct a Uri and use that Uri in a web request. I always get 404
not found. One thing I noticed is that the %5C is converted to a forward
slash ("/") and I don't think it is supposed to be with respect to what the
server is expecting.

Others have passed the harness and have been able to use the above URL but I
don't know what platform they are using.

I am pretty sure it has to do with the %5c. Another URL that fails has the
%2f escape sequence in the path. From what I understand the Uri class ALWAYS
unescapes those two to conform with rfc 3986.

If I understand everything correctly the escape codes %5c and %2f cannot be
used in the path segment when using the Uri class. They can be used in the
query segment, however.

First, can somebody confirm my suspicions?

Secondly, does anybody know how I can work around this?

 

[Jonathan Boivin]

I would try adding a question mark right after the slash next the port.

so : https://IP:PORT/?....

 

[Paul Linville]

Tried that but it didn't work.

I would try adding a question mark right after the slash next the port.

so : https://IP:PORT/?....