Under one Virtual host, I have created an 'External App', like so:
Name: yap
Address: 192.168.1.200:80
Then under 'Rewrite', I have:
Enable Rewrite: yes
Log Level: 9
Rewrite Rules:
RewriteRule ^/(.*)$ http://yap/$1 [P]
-----------------------------------------
But when I try to request anything from this virtual host, the request hangs indefinitely!
error.log says:
015-11-23 16:06:42.804 [INFO] [192.168.1.52:58821] [REWRITE] Rule: Match '/hello.png' with pattern '^/(.*)$', result: 2
2015-11-23 16:06:42.804 [INFO] [192.168.1.52:58821] [REWRITE] Source URI: '/hello.png' => Result URI: 'http://yap/hello.png'
2015-11-23 16:06:42.804 [INFO] [192.168.1.52:58821] [REWRITE] Last Rule, stop!
I use wget to test, and the request looks like this:
$ wget -S "http://litespeed-test.com/hello.png"
--2015-11-23 16:06:42-- http://litespeed-test.com/hello.png
Resolving litespeed-test.com (litespeed-test.com)... 192.168.1.205
Connecting to litespeed-test.com (litespeed-test.com)|192.168.1.205|:80... connected.
HTTP request sent, awaiting response...
And that's it. Will stay like that indefinitely. Needless to say there is another webserver listening on 192.168.1.200:80, and there are no firewalls involved.
Why would Litespeed do this?
Name: yap
Address: 192.168.1.200:80
Then under 'Rewrite', I have:
Enable Rewrite: yes
Log Level: 9
Rewrite Rules:
RewriteRule ^/(.*)$ http://yap/$1 [P]
-----------------------------------------
But when I try to request anything from this virtual host, the request hangs indefinitely!
error.log says:
015-11-23 16:06:42.804 [INFO] [192.168.1.52:58821] [REWRITE] Rule: Match '/hello.png' with pattern '^/(.*)$', result: 2
2015-11-23 16:06:42.804 [INFO] [192.168.1.52:58821] [REWRITE] Source URI: '/hello.png' => Result URI: 'http://yap/hello.png'
2015-11-23 16:06:42.804 [INFO] [192.168.1.52:58821] [REWRITE] Last Rule, stop!
I use wget to test, and the request looks like this:
$ wget -S "http://litespeed-test.com/hello.png"
--2015-11-23 16:06:42-- http://litespeed-test.com/hello.png
Resolving litespeed-test.com (litespeed-test.com)... 192.168.1.205
Connecting to litespeed-test.com (litespeed-test.com)|192.168.1.205|:80... connected.
HTTP request sent, awaiting response...
And that's it. Will stay like that indefinitely. Needless to say there is another webserver listening on 192.168.1.200:80, and there are no firewalls involved.
Why would Litespeed do this?