Proxy context

[adam]

Hi. When configuring a proxy via the "context" feature, is there a way to strip the source path from the request URI before passing through to the backend?

For example, imagine the URI field is set to /api

A request for /api/whatever would be proxied to:

http://backend/whatever

*not*

http://backend/api/whatever

In Apache this would be achieved with a ProxyPass as follows:

ProxyPass /api/ http://backend/

Thanks!

Adam.

 

[Pong]

you can use rewrite rule, please check https://docs.litespeedtech.com/lsws/cp/cpanel/rewrite-proxy/

 

[adam]

Thanks for the reply. That's an option, if this issue is resolvable:

https://www.litespeedtech.com/support/forum/threads/allowencodedslashes.20949/

 

[NiteWave]

ProxyPass /api/ http://backend/

can use rewrite rule to achieve it:

RewriteRule /api/(.*)$ http://backend/$1 [P]

 

[adam]

can use rewrite rule to achieve it:

RewriteRule /api/(.*)$ http://backend/$1 [P]

This works except but it replaces the encoded slashes (as per https://www.litespeedtech.com/support/forum/threads/allowencodedslashes.20949/).

 

[mistwang]

Hi,
You could use Apache style configuration for

ProxyPass /api/ http://backend/

 

[adam]

Hi,
You could use Apache style configuration for

Thanks. This does work but the behavior is the same as with the RewriteRule method, the "AllowEncodedSlashes NoDecode" directive is ignored. The backend API being proxied uses %2F to differentiate slashes in the request URI from slashes in the request params so converting the %2F to / breaks compatibility. Is there any way to mirror the Apache functionality?

Thanks for your assistance.

 

[mistwang]

We will try to support "AllowEncodedSlashes NoDecode", it will take some time, as it is a bigger change.

 

[mistwang]

Please try the latest 6.1RC1 debug build, the "ProxyPass" should work now.
/usr/local/lsws/admin/misc/lsup.sh -d -f -v 6.1RC1