You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Tyk gets the request, and executes my plugin. Note the value of request.RequestURI at this point (from inside the JSVM plugin) is 99999-XXXX+/+dog+9+fff%C3%A9o+party. My plugin does nothing with this value other than log it btw.
The JSVM plugin sets the following request header: X-My-Proxytourl: https://mybackend/bcans
This rewrites the url but the the target backend receives the following instead which fails as the "name" is messed up. Its like the something inside Tyk drops the %2F%2F encoding and replaces it w/ just a single / literally in the url, and mybackend server then improperly parses this path.
The text was updated successfully, but these errors were encountered:
bitsofinfo
changed the title
2.6.4 url rewriter %2F and forward slashes
2.6.4 issues with proxying paths w/ %2F for literal forward slashes
Feb 12, 2019
v2.6.4
Do you want to request a feature or report a bug?
bug
What is the current behavior?
I need get use my beercan api to request beer can by "name" which is literally this string:
99999-XXXX // dog 9 ffféo party
I make a GET request that is url encoded to my API:
Tyk gets the request, and executes my plugin. Note the value of
request.RequestURI
at this point (from inside the JSVM plugin) is99999-XXXX+/+dog+9+fff%C3%A9o+party
. My plugin does nothing with this value other than log it btw.The JSVM plugin sets the following request header:
X-My-Proxytourl: https://mybackend/bcans
Next Tyks URL rewriter runs w/ this config:=
This rewrites the url but the the target backend receives the following instead which fails as the "name" is messed up. Its like the something inside Tyk drops the
%2F%2F
encoding and replaces it w/ just a single/
literally in the url, and mybackend server then improperly parses this path.https://mybackend/bcans/99999-XXXX+/+dog+9+fff%C3%A9o+party
What is the expected behavior?
mybackend should be proxied to with the below:
https://mybackend/bcans/99999-XXXX+%2F%2F+dog+9+fff%C3%A9o+party
Minimized config
The text was updated successfully, but these errors were encountered: