Reverse Proxy Issue.

[fultotop Profile]

I've just installed Helicon Ape on a Windows 2003 server with IIS6 and seems to be having an issue with reverse proxy. I've added the lines to httpd.conf:-

Code: Select all

<Location /sips/cognos>
   ProxyPass http://192.168.10.140:19300
   ProxyPassReverse http://192.168.10.140:19300
</Location>

and in the error.log i get response :-

Code: Select all

[2014-05-22 12:31:36.053] [LicenseManager] Server mode: Trial days left 45. (SiteId= 1)
[2014-05-22 12:31:36.053] [proxy] (debug) [/sips/cognos/p2pd/servlet/dispatch] request to http://192.168.10.140:19300/p2pd/servlet/dispatch?b_action=xts.run&m=portal%2Fmain.xts&m_redirect=/cognos_express/manager/

then I get the 404 page not found in my browser, but if I copy the link from the error.log it works fine. I get the same 404 error if I try and use a RewriteRule for example:-

Code: Select all

RewriteRule /sips/cognos*(.*) http://192.168.10.140:19300$1 [NC,P]

but if I don't proxy but use a redirect such as:-

Code: Select all

RewriteRule /sips/cognos*(.*) http://192.168.10.140:19300$1 [NC]

it redirects fine.

[HeliconAndrew]

Hello,

Where do you make the request, if using the

Code: Select all

<Location /sips/cognos>
   ProxyPass http://192.168.10.140:19300
   ProxyPassReverse http://192.168.10.140:19300
</Location>

Do you make the request from a browser or some page requests this data for itself?

Lets try to test proxying, by using a simple proxying rule:

Code: Select all

<location />
ProxyPass http://www.google.com/
</location>

Regards

[fultotop Profile]

Do you make the request from a browser or some page requests this data for itself?

In a browser.

I tried the proxy test to google and that failed as well it's just giving an Internet explorer 404 webpage. the error.log file contained:-

Code: Select all

[2014-05-22 14:50:49.357] [proxy] (debug) [/] request to http://www.google.com/

[HeliconAndrew]

Hmmm... this is strange. Your options:

a. Email us using the email in contacts and provide us with the remote access to the server. We'll take a look and try to debug it.
b. What was the reason you chose HeliconApe and not ISAPI_Rewrite3 for WS2003? For the testing purposes I'd suggest taking HeliconApe out and installing ISAPI_Rewrite3 instead. Test it. This may change a couple things, since HeliconApe was designed for IIS7+.

Regards
Andrew