Why 'Bad Set-Cookie header ... HttpOnly No '=' found for token starting at position xx' exception occurs after I migrate an application to OCP env?

Solution Verified - Updated -

Issue

  • The below exception occurs after I migrate an application to OCP 3.x env.
ERROR;;HTTPConnectException: Bad Set-Cookie header: xxxxxxxxx=xxxxxxxxxxxxx; path=/; HttpOnly
No '=' found for token starting at position 75;;xxxxxxxxxxxxxx;;0.003
ERROR;;ReceiveException: Error while receiving data from Server :: HTTP_223;;Bad Set-Cookie header: 
xxxxxxxxxxxxx=xxxxxxxxxxxxxxxxxxxx; path=/; HttpOnly
No '=' found for token starting at position x;;
  • The cookie attribute called 'HttpOnly' seems to be delivered at HTTP response like the below and it may cause the above exception.
# curl -I <route> 

HTTP/1.1 200 OK
Content-Length: 11
.......
Set-Cookie: 2daea9393bc1b6a956c599e617ad520f=71d478230cc7f6830fe84a76803c1d13; path=/; HttpOnly <<=====
Cache-control: private 

Environment

  • OpenShift Container Platform (OCP) 3.x

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content