https://bz.apache.org/bugzilla/show_bug.cgi?id=68677
--- Comment #9 from Christopher Schultz <ch...@christopherschultz.net> ---
Back to your original request...
Could you set HTTP headers (to proxy either using AJP or HTTP) and then have
your application pick those up using a Filter? Something like:
Client -- HTTP --> IIS
IIS adds header Request-Attribute-Foo
IIS adds header Request-Attribute-Bar
IIS -- AJP or HTTP --> Tomcat
RequestAttributeFilter grabs all Request-Attribute-* headers
- request.setAttribute("Foo", request.getHeader("Request-Attribute-Foo"))
- request.setAttribute("Bar", request.getHeader("Request-Attribute-Bar"))
I guess what I'm really asking is "do you need this to be implemented in mod_jk
or can you do it another way?"
The reason REMOTE_USER, etc. really need to be done differently is because you
really want the REMOTE_USER and friends to be available as early as possible in
the request-processing pipeline. That's why you would usually use a Valve for
these kinds of things, including before any Authenticator valve runs.
If your application just needs some request attributes, can you grab them this
way? Or, maybe even get them directly from the request headers instead of
attributes?
--
You are receiving this mail because:
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org
