-
1. Re: Problem with Wildfly 10.1.0.Final handling multiple cookies with the same name
gir489 Sep 15, 2017 7:20 AM (in response to _riley_)Not to be confrontational, but what's the use case for this? It sounds like your application would get mixed messages here, with both a yes and a no.
Also, I noticed you have an erroneous quotation mark in your CURL call. Did you mean to do "USER_TOKEN=Yes; USER_TOKEN=No"?
-
2. Re: Problem with Wildfly 10.1.0.Final handling multiple cookies with the same name
_riley_ Sep 15, 2017 7:33 AM (in response to gir489)Thanks for responding. The 'yes' and 'no' are just examples to make the question clearer. I realise this is an odd scenario, but our product is deployed in a huge range of different ways, and this situation can easily occur.
Without going into to much detail, in my situation each cookie would contain a sessionId encoded in a different way (obtained by the user authenticating via different mechanisms), the app would then decide which takes precedent based on how it is encoded.
Hope that helps.
-
3. Re: Problem with Wildfly 10.1.0.Final handling multiple cookies with the same name
_riley_ Sep 15, 2017 8:34 AM (in response to gir489)Yes thanks there was a typo in the curl command. I have now corrected it.
-
4. Re: Problem with Wildfly 10.1.0.Final handling multiple cookies with the same name
richard.hruza Sep 18, 2017 10:34 AM (in response to _riley_)Hello, any update for this case? I suffer with the same issue.
-
5. Re: Problem with Wildfly 10.1.0.Final handling multiple cookies with the same name
gir489 Sep 18, 2017 2:58 PM (in response to richard.hruza)The Wildfly developers would have to address this through a design change. Currently, Undertow uses the name of the cookie as the key in the map it returns. See: undertow/HttpServletRequestImpl.java at master · undertow-io/undertow · GitHub