I've done a draft PR to potentially fix this:
https://github.com/eclipse/jetty.project/pull/10479
But we need to actually write a test to confirm the diagnosis first.
On Tue, 5 Sept 2023 at 17:44, Jan Bartel via jetty-users <
jetty-users@eclipse.org> wrote:
> Silvio,
>
>
> This looks like a url
Silvio,
This looks like a url with the sessionid encoded in the url, but it is
incomplete. It looks like the url just contains JSESSIONID, whereas it
should be JSESSIONID=.
I don't think we changed the way we parse the sessionid from the url since
at least jetty 10, but I could be wrong, I
We use setWorkerName(null) in the Jetty embedding code. It is not in any
URL.
On 04-09-2023 14:03, Bill Ross via jetty-users wrote:
> SessionIdManager.setWorkerName(null)
Maybe SessionIdManager.setWorkerName("")?
34 chars
> 1234567890123456789012345678901234
Bill
--
Phobrain.com
On
I do not know exactly which request causes the issue since I have not
yet debugged that. There may be a UUID in the parameter list but these
have length 36. The issue only occurs in 12.0.1 so I doubt the
URL-paramaters are encoded incorrectly. We never use application
character data in URL
> SessionIdManager.setWorkerName(null)
Maybe SessionIdManager.setWorkerName("")?
34 chars
> 1234567890123456789012345678901234
Bill
--
Phobrain.com
On 2023-09-04 04:58, Bill Ross via jetty-users wrote:
> I wonder if this could be a string encoding issue? Can you think of any
>
I wonder if this could be a string encoding issue? Can you think of any
strings/params that are this long?
1234567890123456789012345678901234
2023-09-04 13:39:27.421:WARN :oejs.Response:qtp105374791-42: writeError:
status=500, message=java.lang.StringIndexOutOfBoundsException: Index 34
out of
I get a runtime exception when using Jetty 12.0.1 in embedded mode
(http/2). I have to add that i call SessionIdManager.setWorkerName(null)
to get rid of the node id in the session ID (which has always worked for
previous versions).
2023-09-04 13:39:27.421:WARN :oejs.Response:qtp105374791-42:
