Why does Apache httpd/mod_ proxy returns HTTP 417 response?

Solution Unverified - Updated -

Issue

When Apache httpd/mod_proxy is used as reverse proxy and it returns HTTP 417 Expectation Failed response. What causes this 417 response and how can I stop this?

12.34.56.111 - - [25/Aug/2017:19:30:00 +0900] "POST /ABC HTTP/1.1" 417 364 "-" "Mozilla/4.0 (compatible; MSIE 6.0; MS Web Services Client Protocol 2.0.50727.8009)"
12.34.56.111 - - [25/Aug/2017:19:31:00 +0900] "POST /ABC HTTP/1.1" 417 364 "-" "Mozilla/4.0 (compatible; MSIE 6.0; MS Web Services Client Protocol 2.0.50727.8009)"
12.34.56.111 - - [25/Aug/2017:19:32:00 +0900] "POST /ABC HTTP/1.1" 417 364 "-" "Mozilla/4.0 (compatible; MSIE 6.0; MS Web Services Client Protocol 2.0.50727.8009)"
12.34.56.111 - - [25/Aug/2017:19:33:00 +0900] "POST /ABC HTTP/1.1" 417 364 "-" "Mozilla/4.0 (compatible; MSIE 6.0; MS Web Services Client Protocol 2.0.50727.8009)"
12.34.56.111 - - [25/Aug/2017:19:34:00 +0900] "POST /ABC HTTP/1.1" 417 364 "-" "Mozilla/4.0 (compatible; MSIE 6.0; MS Web Services Client Protocol 2.0.50727.8009)"
:

Here's configuration:

<Location /ABC>
ProxyPass http://example.com:80/abc
ProxyPassReverse http://example.com:80/abc
</Location>
:
SetEnv force-proxy-request-1.0 1
:

Environment

  • Red Hat Enterprise Linux (RHEL) 7
  • Red Hat Enterprise Linux (RHEL) 6
  • Apache httpd

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.