Hello everyone,
I am currently working on setting up a reverse proxy that directs traffic to a Docker container, and I've hit a bit of a snag.
My application requires that certain URLs containing encoded slashes (%2F) be passed to the Docker container without being decoded or altered.
For example, if a user accesses http://example.com/api/v1/data/a/b, I need the reverse proxy to forward the request exactly as http://example.com/api/v1/data/a/b (with %2F intact), instead of decoding it to http://example.com/api/v1/data/a/b.
In Apache there is 'AllowEncodedSlashes NoDecode' but i cant find anything similar or a workaround for openlightspeed
Has anyone faced a similar issue or knows a way to configure the reverse proxy to forward the URL without decoding the slashes? Any guidance or examples of configuration files would be greatly appreciated!
Thanks in advance!
I am currently working on setting up a reverse proxy that directs traffic to a Docker container, and I've hit a bit of a snag.
My application requires that certain URLs containing encoded slashes (%2F) be passed to the Docker container without being decoded or altered.
For example, if a user accesses http://example.com/api/v1/data/a/b, I need the reverse proxy to forward the request exactly as http://example.com/api/v1/data/a/b (with %2F intact), instead of decoding it to http://example.com/api/v1/data/a/b.
In Apache there is 'AllowEncodedSlashes NoDecode' but i cant find anything similar or a workaround for openlightspeed
Has anyone faced a similar issue or knows a way to configure the reverse proxy to forward the URL without decoding the slashes? Any guidance or examples of configuration files would be greatly appreciated!
Thanks in advance!
