Project

General

Profile

Bug #1763

mod_proxy_backend_ajp13 is cleaning request_uri

Added by Anonymous about 11 years ago. Updated almost 11 years ago.

Status:
Wontfix
Priority:
Normal
Assignee:
-
Category:
mod_proxy_backend_ajp13
Target version:
Start date:
Due date:
% Done:

0%

Estimated time:
Missing in 1.5.x:

Description

subset of my conf file


server.modules = ( "mod_proxy_core", "mod_proxy_backend_ajp13")
$HTTP["host"] == "sub.domain.com" {
   proxy-core.balancer = "round-robin" 
   proxy-core.protocol = "ajp13" 
   proxy-core.backends = ( "localhost:8009" )
   proxy-core.max-pool-size = 25
}

i want to be able to use this URL:


http://sub.domain.com/folder/http://www.cnn.com

however, tomcat ends up seeing the following path


/folder/http/www.cnn.com

i want to avoid the URI munging. if i were to use tomcat directly, this munging doesn't happen...

-- eleith

History

#1

Updated by stbuehler about 11 years ago

  • Status changed from New to Fixed
  • Resolution set to wontfix

Just use the "REQUEST_URI" var to get the original uri; all "sane" url handling wants a clean path without things like "//" and "/../".

#2

Updated by Anonymous about 11 years ago

  • Status changed from Fixed to Need Feedback
  • Resolution deleted (wontfix)

we are using REQUEST_URI, and we are losing access to the original URI.

if we use mod_proxy_backend_http, request_uri is not cleaned (as expected), but when using ajp13, our request_uri is cleaned.

we have had to switch to using the http proxy in order to get the expected results.

-- eleith

#3

Updated by stbuehler almost 11 years ago

  • Status changed from Need Feedback to Wontfix
  • Assignee deleted (jakabosky)
  • Patch available set to No

It looks like there is no possibility in ajp13 to send the original uri and the decoded and sanitized and rewritten one. Imho sending only the original uri is not an option, so i will close this again as wontfix.

If you have a better idea please share it with us, thx.

Also available in: Atom