[Bug 68677] no support for enviroment variables/request attributes

2024-02-28 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=68677 --- Comment #10 from dub...@gmail.com --- First off, what I'm asking for already exists in mod_jk via the JkEnvVar directive. I just want the same thing for jk_isapi_plugin (the IIS equivalent of mod_jk). This request stemmed from a deep dive

[Bug 68677] no support for enviroment variables/request attributes

2024-02-28 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=68677 --- Comment #9 from Christopher Schultz --- 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 II

[Bug 68677] no support for enviroment variables/request attributes

2024-02-28 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=68677 --- Comment #8 from Christopher Schultz --- I've proposed making arrangements for REMOTE_USER on the dev list. I realize that's not quite what you are asking for, here, but I thought I'd mention it since I really do think we as a community shou

[Bug 68677] no support for enviroment variables/request attributes

2024-02-28 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=68677 dub...@gmail.com changed: What|Removed |Added Severity|normal |enhancement -- You are receiving th

[Bug 68677] no support for enviroment variables/request attributes

2024-02-28 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=68677 --- Comment #7 from dub...@gmail.com --- Im stuck with IIS, hence the request for a mod to the isapi filter connector. If I could use Apache, I would be able to use the JkEnvVar directive. -- You are receiving this mail because: You are the as

[Bug 68677] no support for enviroment variables/request attributes

2024-02-28 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=68677 --- Comment #6 from Christopher Schultz --- (In reply to dub357 from comment #5) > How would things like REMOTE_USER or the client > certificate get propagated to Tomcat? This is something your presentation > fails to discuss and is arguably t

[Bug 68677] no support for enviroment variables/request attributes

2024-02-28 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=68677 --- Comment #5 from dub...@gmail.com --- Again - I need something integrated w/ Tomcat and a true reverse proxy over HTTP will never be that. How would things like REMOTE_USER or the client certificate get propagated to Tomcat? This is somethi

[Bug 68677] no support for enviroment variables/request attributes

2024-02-28 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=68677 --- Comment #4 from Christopher Schultz --- The typical way to do this is: 1. Remove all inbound HTTP headers you want to set at the proxy 2. Set your specific HTTP headers at the proxy 3. Read your now-trusted HTTP headers from the request in

[Bug 68677] no support for enviroment variables/request attributes

2024-02-27 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=68677 --- Comment #3 from dub...@gmail.com --- I'm not entirely sure, but the point here is that I dont want to use on HTTP headers. The current ISAPI filter already passes on those. The problem is that they can be spoofed by the client so I'm hopin

[Bug 68677] no support for enviroment variables/request attributes

2024-02-27 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=68677 --- Comment #2 from Christopher Schultz --- Does IIS have the ability to add request headers to proxied requests? For example, if you were using client -> [HTTP] -> IIS -> [HTTP] -> Tomcat, would you be able to set arbitrary HTTP headers into t

[Bug 68677] no support for enviroment variables/request attributes

2024-02-26 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=68677 dub...@gmail.com changed: What|Removed |Added OS||All --- Comment #1 from dub...@gmail