Apache httpd proxied application gets status 408 on the backend

Solution Verified - Updated -


  • Some requests fail on the web site with status 502 (Bad Gateway). The requests are reverse proxied to a backend server and the corresponding request is logged there with status 408 (Request Timeout).

    The front end server (Apache httpd working as reverse proxy) access log shows:

    [08/May/2019:08:41:46 +0200] "POST /myapp/index.php HTTP/1.1" 502 418 "https://myfront/myapp/index.php" "Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Firefox/60.0" "" + TLSv1.2 ECDHE-RSA-AES256-GCM-SHA384

    The back end server (another Apache httpd running mod_php) access log shows:

    [08/May/2019:08:41:46 +0200] "POST /myapp/index.php HTTP/1.1" 408 221 "https://myfront/myapp/index.php" "Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Firefox/60.0" "" - - -


  • Red Hat Enterprise Linux (RHEL) 7
  • Red Hat Software Collections (RHSCL) 2.0+
  • Red Hat JBoss Web Server (JWS) 3.0+
  • JBoss Core Services (JBCS) 2.4.23+
  • Apache httpd 2.4

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.

Current Customers and Partners

Log in for full access

Log In