Trouble: css 1150 vs. apache mod_proxy

Unanswered Question
Aug 4th, 2008
User Badges:


I configured a server Apache http as the frontend which receives requests from customers and in turn forwards through the module (mod_proxy) a container with two services (http servers) configured in a css 11500. mod_proxy used persistence on the connections to backends (ccs vp).

After much operate properly are presented to customers error http 503 (service not available). Through a review and sniffer detects that the Apache mod_proxy does not close connections (half-close) or closed many minutes later.

What changes do recommend on CSS to be compatible with Apache mod_proxy?

  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
sachinga.hcl Mon, 08/04/2008 - 18:01
User Badges:
  • Silver, 250 points or more

I presume you are talking about using SSL between the reverse proxy and

the backend? (generally SSL is not really necessary in such


Do you have "SSLProxyEngine On" configured?

Obvious question: Is port 443 open on the intermediate FW?

But a quick check on google (hint, hint...) reveals this is the error =

you get when trying to pass through a proxy with an HTTP method that is =

not supported by the proxy.

Check out this message and the faq link therein (it's about subversion =

but it's the same problem).

In your case, the client must use the CONNECT method to tell the proxy =

to pass the requests directly to the internal server. For this to work =

you need:

- mod_proxy_connect (not just mod_proxy)

- AllowCONNECT 443 (or not present - this is the default)


for details.

sachin garg


This Discussion