Thank you for your response. I don't see how the Tomcat documentation can be fixed unless the Tomcat's Servlet APIs are going to deviate from the Servlet 3.1 specification. If Tomcat continues to deviate from the specification, I don't see how Tomcat 8.5 can claim Servlet 3.1 compliance.
Do you see a way to get the Tomcat cookie implementation to align with the Servlet 3.1 API specification? Can you elaborate on why Tomcat has decided to deviate from the specification in this respect? Is there a reason we cannot fix the behavior (especially if the cookie version is explicitly set)? Thanks! Rob On Fri, Sep 2, 2016 at 4:46 PM, Rémy Maucherat <r...@apache.org> wrote: > 2016-09-02 23:19 GMT+02:00 Robert Winch <rwi...@gmail.com>: > > > I realize that I can manually configure LegacyCookieProcessor > > > > Yes, you'll have to configure the legacy cookie processor to support the > less formal former cookie RFCs, this is as expected. If you find any > discrepancies about that in the Tomcat documentation, you may file a bug. > The default will remain to use the current cookie RFC. > > Rémy >
