Details
-
Bug
-
Status: Open
-
Major
-
Resolution: Unresolved
-
5.16.1
-
None
-
None
Description
There was a defect: AMQ-6571.
It was fixed, but after changing HttpClient and deprecating some cookie policy, HttpTransport changed cookie transport to DEFAULT is reverting AMQ-6571 and causing that cookie in proper (standard) format is not accepted:
2022-02-08 09:33:03,213 WARN [ActiveMQ InactivityMonitor Worker] [] ResponseProcessCookies - Invalid cookie header: "Set-Cookie: visid_incap_2728520=CG9VG5JLS0G1CPBkbkki6IwqAmIAAAAAQUIPAAAAAACRk2zteKSpqYiAk+oxSH4E; expires=Wed, 08 Feb 2023 08:17:31 GMT; HttpOnly; path=/; Domain=.blablabla.com". Invalid 'expires' attribute: Wed, 08 Feb 2023 08:17:31 GMT 2022-02-08 09:33:03,213 WARN [ActiveMQ InactivityMonitor Worker] [] ResponseProcessCookies - Invalid cookie header: "Set-Cookie: ___utmvmSauwmYsZ=a; Max-Age=0; path=/; expires=Sat, 05 Feb 2022 08:10:54 GMT". Invalid 'expires' attribute: Sat, 05 Feb 2022 08:10:54 GMT
Switching to: STANDARD we were able to patch and fix on our side:
requestConfigBuilder.setCookieSpec(CookieSpecs.STANDARD)