Reverse proxy issues
PostPosted:Mon Apr 26, 2010 9:00 pm
Hi,
I'd like to use an apache reverse proxy with URL rewriting in front of OpenKM 4.1RC1. This appears to mostly work as intended, but in the log I see messages like these:
Also, what's the correct solution to this problem? Analysing the http traffic between apache and openkm, I can see stuff like this:
What would be the best way to tell jboss to accept /dms as equivalent to /OpenKM in these POST requests? (The _target_ of the request is correctly rewritten by apache to /OpenKM, only the content isn't.)
Or do I need to find some way to rewrite the content of the HTTP requests before submitting them to jboss? That would not be nice.
Thanks.
I'd like to use an apache reverse proxy with URL rewriting in front of OpenKM 4.1RC1. This appears to mostly work as intended, but in the log I see messages like these:
Code: Select all
Should I be worried?22:33:55,616 INFO [[/OpenKM]] ERROR: The module path requested, /dms/es.git.openkm.frontend.Main/, is not in the same web application as this servlet, /OpenKM. Your module may not be properly configured or your client and server code maybe out of date.
22:33:55,616 INFO [[/OpenKM]] WARNING: Failed to get the SerializationPolicy '6B9DF8C4DDF966DC04215E0FDD070F70' for module 'https://mydomain.net/dms/es.git.openkm.frontend.Main/'; a legacy, 1.3.3 compatible, serialization policy will be used. You may experience SerializationExceptions as a result.
Also, what's the correct solution to this problem? Analysing the http traffic between apache and openkm, I can see stuff like this:
Code: Select all
Now, apparently jboss is troubled that the apparent path of the webapp, /dms, doesn't match the hard-coded default of /OpenKM. It only learns of the apparent path because the browser actually submits a POST request where the content includes it. (Does this behaviour serve a useful purpose?)POST /OpenKM/OKMAuthServlet HTTP/1.1
Host: openkm.host.internal:8080
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10_6_3; de-de) AppleWebKit/531.22.7 (KHTML, like Gecko) Version/4.0.5 Safari/531.22.7
Origin: https://mydomain.net
Content-Type: text/x-gwt-rpc; charset=utf-8
Referer: https://mydomain.net/dms/es.git.openkm.frontend.Main/6BCA55867A700DFC0FE70E88A199EDC9.cache.html
Accept: */*
Accept-Language: de-de
Accept-Encoding: gzip, deflate
Cookie: JSESSIONID=7D0E4CFA74BB25681DFF10B62551EDB0
Via: 1.1 mydomain.net
X-Forwarded-For: 172.18.24.48
X-Forwarded-Host: mydomain.net
X-Forwarded-Server: mydomain.net
Connection: Keep-Alive
Content-Length: 256
5|0|6|https://mydomain.net/dms/es.git.openkm.frontend.Main/|225BFC1814D68B2C24521C8732E099F1|es.git.openkm.frontend.client.service.OKMAuthService|getGrantedUsers|java.lang.String|/okm:root/STR/somefile.DOC|1|2|3|4|1|5|6|
What would be the best way to tell jboss to accept /dms as equivalent to /OpenKM in these POST requests? (The _target_ of the request is correctly rewritten by apache to /OpenKM, only the content isn't.)
Or do I need to find some way to rewrite the content of the HTTP requests before submitting them to jboss? That would not be nice.
Thanks.