Hi,
Using IIS 5, Tomcat 4.1.24 and JK2 as connector:
Have servlets registered in workers2.properties as, EG,
[uri:/servlet/MyServlet]
info=My servlet
context=/
debug=1
For examples sake will call the server "myserver".
The redirection works fine for users accessing "myserver" directly. The successful query looks like this and is fine:
HTTP POST /servlet/MyServlet
For users going via a proxy, however, the servlet POST has been prepended with the server name in transit, so the POST is changed to:
HTTP POST
Obviously this is not registered in jk2, and so we get a 405 Resource Not Allowed.
Ive tried registering the full URL but that still fails, and anyway, jk2 expects all URIs to start with a slash. So these dont work either:
[uri:*/servlet/MyServlet] or [uri:]
Is there a way to prevent this modification of the query? Should it be done via config of the proxy, or somewhere in jk2/IIS/Tomcat.
Thanks alot in advance for any help.
DB.
Using IIS 5, Tomcat 4.1.24 and JK2 as connector:
Have servlets registered in workers2.properties as, EG,
[uri:/servlet/MyServlet]
info=My servlet
context=/
debug=1
For examples sake will call the server "myserver".
The redirection works fine for users accessing "myserver" directly. The successful query looks like this and is fine:
HTTP POST /servlet/MyServlet
For users going via a proxy, however, the servlet POST has been prepended with the server name in transit, so the POST is changed to:
HTTP POST
Obviously this is not registered in jk2, and so we get a 405 Resource Not Allowed.
Ive tried registering the full URL but that still fails, and anyway, jk2 expects all URIs to start with a slash. So these dont work either:
[uri:*/servlet/MyServlet] or [uri:]
Is there a way to prevent this modification of the query? Should it be done via config of the proxy, or somewhere in jk2/IIS/Tomcat.
Thanks alot in advance for any help.
DB.