You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When a request enters jetty, the SessionHandler needs to see the list of cookies and calls org.eclipse.jetty.server.Request.getCookies() which parses them. Later on, application code calls org.eclipse.jetty.ee9.nested.Request.getCookies() to retrieve the list of cookies. Unfortunately the nested Request maintains a completely separate list of cookies and cookie parsing state, so thus parses them all over again. Moreover, it parses them differently to the o.e.j.s.Request.
For example, given the following cookie header, and a compliance mode of RFC6265: $Version="1"; name1="value1"; $Path="/servlet_jsh_cookie_web"; $Domain="localhost"
The o.e.j.s.Request parsing produces the (correct) list:
The o.e.j.ee9.n.Request parsing produces the (incorrect) list: name1="value1"
The text was updated successfully, but these errors were encountered:
janbartel
added
Bug
For general bugs on Jetty side
TCK
For various Specification Test Compatibility Kits (eg: Servlet, WebSocket, HTTP/2, etc)
labels
May 11, 2023
Relevant tck tests:
When a request enters jetty, the
SessionHandler
needs to see the list of cookies and callsorg.eclipse.jetty.server.Request.getCookies()
which parses them. Later on, application code callsorg.eclipse.jetty.ee9.nested.Request.getCookies()
to retrieve the list of cookies. Unfortunately the nested Request maintains a completely separate list of cookies and cookie parsing state, so thus parses them all over again. Moreover, it parses them differently to theo.e.j.s.Request
.For example, given the following cookie header, and a compliance mode of
RFC6265
:$Version="1"; name1="value1"; $Path="/servlet_jsh_cookie_web"; $Domain="localhost"
The
o.e.j.s.Request
parsing produces the (correct) list:The
o.e.j.ee9.n.Request
parsing produces the (incorrect) list:name1="value1"
The text was updated successfully, but these errors were encountered: