Feature #152: mod_proxy feature to remove part of the URI when passing along requests... - Lighttpd - lighty labs

Actions

Copy link

Feature #152

closed

mod_proxy feature to remove part of the URI when passing along requests...

Added by Anonymous almost 19 years ago. Updated almost 7 years ago.

Status:

Fixed

Priority:

Low

Category:

mod_proxy

Target version:

1.4.46

ASK QUESTIONS IN Forums:

Description

With mod_proxy, there's currently no way to let you map requests from http://somedomain.com/path/ to http://internalserver/. This is because the proxy will pass /path/ as the request URI to 'internalserver' instead of '/'.

mod_proxy needs to have an extra setting that either says "remove <extension> from the target URI", or "remove this from the target URI: '/somepath/'".

Actions

Copy link

Updated by Anonymous almost 19 years ago

I think this would be very useful too. It is like ProxyPass and ProxyPassReverse for apache.

-- miles.wu

Actions

Copy link

Updated by Anonymous over 18 years ago

Add another vote for this.

-- cpisto

Actions

Copy link

Updated by Anonymous over 18 years ago

Add another vote for this.

-- cpisto

Actions

Copy link

Updated by Anonymous almost 18 years ago

-- zimbatm

Actions

Copy link

Updated by Anonymous over 17 years ago

I could use this feature as well

I'm currently using mod_rewrite to 'fix' the URI before it is processed on the target system.

Actions

Copy link

Updated by gstrauss almost 8 years ago

Description updated (diff)
Assignee deleted (~~jan~~)
Priority changed from High to Low

Much of what is requested here can be done by writing custom lua code and using mod_magnet. Another alternative is to use the scripting language of your choice to do the translation on the backend server that receives the proxied request.

However, to add this to lighttpd configuration settings is not a minor enhancement -- it would be a substantial amount of work. Supporting "Apache-style" ProxyPass and ProxyPassReverse would also require writing a user-interface to support various, complex, user-configurable settings, even if that user-interface was similar to Apache ProxyPass and ProxyPassReverse. When there were many fewer "programmers" than there are now, maybe learning how to program the "Apache-style" config language was more worthwhile than it is today. Today, I would suggest learning a scripting language is, at least in some cases, more worthwhile than learning the "Apache-style" config language.

Actions

Copy link