Hi Silvio, I don't really understand what you're trying to do, but as far as session ids go:
* jetty has always appended "."+workername to the session id for the jsessionid cookie/url param. This tells a load balancer which jetty instance to direct subsequent requests to. * for a while now (can't remember in which jetty release, but it was a while ago) we started also prepending the workername to the session id to try and ensure the id was unique within the cluster. We've had always had handling in place if the workername was null. But I think in 9.4 we have opted to always default it to a value, and there may be new parts of the code that expect it won't therefore be null. I'll have a look at it for 9.4.1. Meanwhile, you can also override the DefaultSessionIdManager.getExtendedId(String, HttpServletRequest) to just return the id without the .workername appended. Jan On 5 January 2017 at 02:12, Silvio Bierman <[email protected]> wrote: > To clarify my previous post: Jetty seems to append a dot and the worker > name to the subsequent session IDs (created from requests originatin in the > server itself). It does not do this when the requests come from the outside. > > Since I set the workername to empty to get rid of the worker name prefix > this results in only a dot being appended. > > To double-check I tested with a build that reverts to 9.3 and it is > definitely a 9.4 issue. > > Cheers, > > Silvio > > > > On 01/04/2017 12:28 PM, Silvio Bierman wrote: > >> Hello all, >> >> I have an issue with session IDs generated by Jetty in my application >> that embeds Jetty 9.4. >> >> Initially I had the problem that Jetty prepends a worker name into the >> session ID. Someone here suggested I override the session ID generation >> (which I already do in clustered mode). But setting the worker name to an >> empty string appeared to work fine so I went for that. >> >> But: on subsequent sessions that are generated by requests that come from >> the server itself Jetty appends a single dot (.) to newly created session >> IDs. Many URL handling user code (which I have limited influence on) is not >> prepared for this so many user scripts no longer work. >> >> I attempted to resolve this by overriding >> DefaultSessionIdManager#newSessionId >> after all and explicitly filtering out the dot. But to my surprise the >> session ID returned from there does not contain a dot. Instead it is >> appended at some later stage. >> >> How can I get full control over session ID generation to get rid of any >> session id decoration? >> >> Thanks in advance, >> >> Cheers, >> >> Silvio >> >> _______________________________________________ >> jetty-users mailing list >> [email protected] >> To change your delivery options, retrieve your password, or unsubscribe >> from this list, visit >> https://dev.eclipse.org/mailman/listinfo/jetty-users >> > > _______________________________________________ > jetty-users mailing list > [email protected] > To change your delivery options, retrieve your password, or unsubscribe > from this list, visit > https://dev.eclipse.org/mailman/listinfo/jetty-users > -- Jan Bartel <[email protected]> www.webtide.com *Expert assistance from the creators of Jetty and CometD*
_______________________________________________ jetty-users mailing list [email protected] To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/jetty-users
