Ticket #674 (closed defect: invalid)

Opened 2 years ago

Last modified 3 weeks ago

mod_proxy needs to behave like mod_proxy on apache.

Reported by: anonymous Assigned to: jan
Priority: normal Milestone:
Component: mod_proxy Version: 1.4.11
Severity: minor Keywords:
Cc: Blocking:
Need Feedback: 0

Description

Since url rewrites and proxying don't work properly inside a $HTTPurl?{}, we should have some method of telling proxy.server the path we want to proxy to. So you can forward http://lighttpd/path/wibble.html to a backend such as http://backend/some/other/path/wibble.html

Attachments

Change History

03/21/2007 12:40:07 PM changed by anonymous

Any idea if this will ever get seen to? Hints on a workaround might also be nice.

03/22/2007 09:53:28 AM changed by anonymous

What you're looking for is internal rewrites of proxied requests.

I don't know if that is supported if:

  • load mod_rewrite before mod_proxy in modules list
  • tell mod_proxy to handle the rewritten URLs

??

Or maybe this is where Jan is likely to say "can be done with mod_magnet / LUA"?

04/25/2008 02:20:05 PM changed by stbuehler

  • status changed from new to closed.
  • resolution set to invalid.
  • blocking changed.
  • pending changed.

That you cannot use rewrite in url conditionals is no limitation as you can check the same things in the rewrite pattern as you had in your url conditional.

Add/Change #674 (mod_proxy needs to behave like mod_proxy on apache.)




Change Properties
Action