Handling Expect: 100-continue response headers in OpenShift 4.14+
Issue
- Client calls to backend applications with
Expect: 100-continuefail or time out when routed through OpenShift Routes. - How to manage or modify request or response headers on OpenShift 4?
-
Is the header
Expect: 100-continuedsupported on OpenShift? -
Connections to applications via route time out or get reset when the header
Expect: 100-continueis included:
Recv failure: Connection reset by peer
Closing connection 0
curl: (56) Recv failure: Connection reset by peer
- Alternative error codes may look like:
> GET /example-testing HTTP/1.1
> Host: <test-address>
> User-Agent: curl/7.61.1
> Accept: */*
> Expect: 100-Continue
> Content-Type: application/json
> Authorization: Bearer <token>
>
< HTTP/1.1 100 Continue
Long wait between these two
< HTTP/1.1 502 Bad Gateway
< content-length: 107
< cache-control: no-cache
< content-type: text/html
<
<html><body><h1>502 Bad Gateway</h1>
The server returned an invalid or incomplete response.
</body></html>
Environment
- Red Hat OpenShift Container Platform (RHOCP) 4.14+
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.
