|Re: [jetty-users] Issues with Jetty 9.4 session IDs|
Thank you for the reply.
Perhaps worker name decoration has existed before 9.4 but then the default worker name was probably null so we never say any worker name related things in the session IDs. Now my worker name seems to default to "node0" and setting it to null gives an NPE early during server startup. Therefore I opted for "" but that leaves the dot suffix. I guess reintroducing null handling would solve my problems.
Firstly we have our own clustering logic that uses session ID decoration and relies on some assumptions about what a default session ID looks like. Both the increased length and the presence of a dot breaks some of those assumptions.
Secondly our system runs user defined/manipulated scripts that tend to do a lot of fiddling with URLs. Many scripts naively look for a dot in the URL to find extensions like ".pdf" and replace that with ".html" etc. Since we have the session ID in the URL many of these scripts now fail because of the dot.
Finally we have one special case where we need to use a session ID that is a checksum-padded UUID primary key (only used for server-server communication behind the firewall). We used to do this by overriding newSessionId.
I tried overriding getExtendedId but that does not help. The dot is still appended afterwards.
On 01/06/2017 12:42 AM, Jan Bartel wrote:
Back to the top