# Nginx behind mod\_proxy giving 408

**URL:** <https://www.ruby-forum.com/t/nginx-behind-mod-proxy-giving-408/195280>\
**Category:** NGINX\
**Created:** [September 21, 2010, 2:31am UTC](https://www.ruby-forum.com/t/nginx-behind-mod-proxy-giving-408/195280 "2010-09-21T02:31:43Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![ajassal](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/a/c37758/32.png) [@ajassal](https://www.ruby-forum.com/u/ajassal)\
**Post date:** [September 21, 2010, 2:31am UTC](https://www.ruby-forum.com/t/nginx-behind-mod-proxy-giving-408/195280/1 "2010-09-21T02:31:43Z")

</div>

As part of rolling out nginx across our site, we are doing a phased  
roll-out of services currently running behind apache (mod\_proxy).

For our first service we have nginx running behind apache (mod\_proxy)  
for some URLs.  
This is causing issues for certain POST requests where status returned  
is 408 in nginx and lines such as

[Mon Sep 20 14:31:55 2010] [error] [client xxx] proxy: Error reading  
from remote server returned by /xxxx  
[Mon Sep 20 14:32:01 2010] [error] [client xxx] (70014)End of file  
found: proxy: error reading status line from remote server xxx

appear in apache error log.

Increasing client\_body\_timeout does not an impact.

Comments?

Posted at Nginx Forum:

> **[nginx behind mod\_proxy giving 408](https://forum.nginx.org/read.php?2,132397,132397#msg-132397)**
>
> As part of rolling out nginx across our site, we are doing a phased roll-out of services currently running behind apache (mod\_proxy). For our first service we have nginx running behind apache (mod\_proxy) for some URLs. This is causing issues for...