https://issues.apache.org/bugzilla/show_bug.cgi?id=50707
Summary: Apache not using the ProxyRemote directive
consistently
Product: Apache httpd-2
Version: 2.2.17
Platform: PC
OS/Version: Linux
Status: NEW
Severity: blocker
Priority: P2
Component: mod_proxy
AssignedTo: [email protected]
ReportedBy: [email protected]
Created an attachment (id=26595)
--> (https://issues.apache.org/bugzilla/attachment.cgi?id=26595)
Packet Capture File
Hi,
I'm seeing a weird Apache behavior.
I;ve got an apache server configured as a proxy which sends all of its request
via another proxy out to the internet using the ProxyRemote directive. The
secong apache acts as a GW to connect to internet.
ProxyRemote http http://<hostname>:80
We are now seeing this weird behavior:
1. Client requests URL
2. Apache forwards this request to the second apache in chain
3. The GW tears down the tcp connection.
4. Apache retries the HTTP request, however this time it tries to connect
directly to the OS instead of going through the GW
5. The OS replies directly to apache with a HTTP status code
6. The HTTP status code reply is sent to the client
The question is: how come Apache(httpd) is connecting directly to the OS when
the GW tears down the connection? Is this the expected Apache 2 behavior in
this scenario? Is there any way to avoid it?
I've been browsing the Apache 2.x documentation but could not find anything
that explains this behavior, could it be caused by our ngp_module?
I'm guessing that it may be related to load on teh second proxy if Apache can't
connect to it then it trys a direct connection??
Thanks a lot.
- Shashank
--
Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
