[Netty 5] HTTP Cookies
See original GitHub issueWe should investigate a few changes to the Cookies
API:
- Support Cookies with the same name as described in RFC-6265 (section 4.2.2)
- Investigate support of the SameSite attribute ( https://tools.ietf.org/html/draft-west-first-party-cookies-07 )
Issue Analytics
- State:
- Created 5 years ago
- Reactions:4
- Comments:7 (5 by maintainers)
Top Results From Across the Web
Cookies (reactor-netty 1.0.5 API) - Project Reactor
Parameters: headers - client response headers; Returns: a new cookies holder from client response headers. newServerRequestHolder.
Read more >Package io.netty5.handler.codec.http.cookie
Module io.netty5.codec.http ... Cookie. An interface defining an HTTP cookie. ... A RFC6265 compliant cookie decoder to be used client side.
Read more >Netty - cannot set multiple cookies with one CookieEncoder
It's actually a violation of HTTP cookie specification to set multiple cookies in a Set-Cookie header. You ...
Read more >io.micronaut.http.netty.cookies (micronaut 1.2.5 API)
Package io.micronaut.http.netty.cookies. Netty Cookies. See: Description. Class Summary. Class, Description. NettyCookie. A wrapper around a Netty cookie.
Read more >How to use DefaultCookie in io.netty.handler.codec.http.cookie
... @NonNull String value, int maxAge, boolean secured) { Cookie nettyCookie = new io.netty.handler.codec.http.cookie.DefaultCookie(name, value);
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
FYI: Google Chrome announced changes in the default behavior: cookies without explicitly specified SameSite attribute will be treated by default as SameSite=Lax instead of SameSite=None. So far it looks like it won’t be enabled earlier than the end of this year, but it makes the need for the new feature more urgent, since many of the existing solutions that have cookies that need to be available in a third-party context would break.
@tlunter see #10050