[Resolved] ProxyPass Configuration using Proxy in Litespeed

[Elik]

Hello,

I have been trying to setup the tomcat proxy so that person can use tomcat to pass it to Tomcat. I have setup in the External App the setting for Tomcat to be proxied at port 8080 using Webserver Setting.

Then I add in the .htaccess this line:

RewriteEngine On
RewriteRule ^/(.*)$ http://127.0.0.1:8080/$1 [L,P,QSA]

But it does not work, since it give error 500 when I tried it. I used the information I found from the forum to do the Reverse Proxy so I can redirect requests to tomcat for servlets, and such, and it is not working properly as it should be for it. So...any help here?

Note that it fails since it could not find the file, home.do in the directory, but tomcat picks it up when tried directly, but not from litespeed proxy itself.

Here is the reference link to the other post, which I used to setup the Tomcat Proxy which it did not work for it. http://www.litespeedtech.com/support/forum/showthread.php?t=2879

 

[NiteWave]

Maybe you've missed the last post in that thread?

repost it here:

RewriteRule (.*) http://127.0.0.1:port/$1 [p]

should work.
You have to remove the leading '/' if you use the rewrite rule in .htaccess.

 

[Elik]

I did that. It does not work with or without it with that Rewrite Rule part for it to proxy it. The problem is that Litespeed do not recognize the non-existant filename like home.do which is mapped by the servlet to have it load.

Here is the example site:

Non-Working: http://vishalwedsaditi.com/home.do
Working: http://vishalwedsaditi.com:8080/home.do

 

[NiteWave]

I have setup in the External App the setting for Tomcat to be proxied at port 8080 using Webserver Setting.

assume the external app name is tomcat_backend. Please try following instead:

RewriteEngine On
RewriteRule (.*) http://tomcat_backend/$1 [L,P,QSA]

I did similar test locally, and passed.

 

[Elik]

Thanks

Now we getting somewhere with this. Now I able to get it passed to Tomcat with that example. Now I gotta see how to get tomcat to recognize the home.do as well for it to load.

Nevermind, seems the client been mucking around with it, causing it not to load at this point, but the tomcat proxy is working properly now. I appreciate the help!