Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I am about to setup a reverse proxy server to filter and log page requests before relaying the actual content from the origin server. (new to this)

Before this, I had the origin server public facing, and I had php5 configured to accept 20 Mb file uploads for my php web-app.

Now that I am sticking the proxy server in between, are there any special configurations that I should consider to make sure things such as file-transfer are still relayed properly between the client and the origin server?


share|improve this question
up vote 1 down vote accepted

This depends very much on the reverse proxy you are using, as they tend to have different default max request body lengths.


Apache - defaults to unlimited, it can be set using LimitRequestBody

Nginx - defaults to 1MB, it can be changed using client_max_body_size

Squid - defaults to unlimited, it can be set using request_body_max_size

There may also be request body read timeouts, such as Nginx's client_body_timeout which is set to 60 seconds, which may affect people on slower/bad connections.

share|improve this answer
I am using Apache - I will look into the parameter you suggested and the same for time-out limits. Thanks @Andy! – Anson Kao Dec 11 '10 at 20:40
A note about the limitrequestbody: Note: not applicable to proxy requests. Per – user235375 Jul 31 '14 at 1:19

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.