AWS behind mod_proxy returns corrupt headers

Solution Verified - Updated -

Issue

  • We have AWS behind mod_proxy. We occasionally see bad response headers returned by AWS through the proxy, such as the sample below with an extra 0 line before the expedcted headers:
0
HTTP/1.1 200 OK
Cache-Control: no-cache
...

Environment

  • Red Hat Enterprise Linux (RHEL)
    • Apache httpd
      • mod_proxy_http
  • AWS

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
Close

Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.