Warnings printed out for HTTP/2 Settings

[lprimak]

Started seeing these in the logs. Not readily reproducible but appears with the later versions of Grizzly 4.0.0
Maybe has something to do with Chrome but I am not sure.

[#|2024-03-14T16:09:23.862+0000|WARNING|Payara 6.2024.3|org.glassfish.grizzly.http2.frames.SettingsFrame|_ThreadID=91;_ThreadName=http-thread-pool::http-listener-2(3);_TimeMillis=1710432563862;_LevelValue=900;|
  Setting 2,794 is unknown and will be ignored|#]

[#|2024-03-14T16:09:32.167+0000|WARNING|Payara 6.2024.3|org.glassfish.grizzly.http2.frames.SettingsFrame|_ThreadID=90;_ThreadName=http-thread-pool::http-listener-2(2);_TimeMillis=1710432572167;_LevelValue=900;|
  Setting 6,714 is unknown and will be ignored|#]

See also payara/Payara#6587

[lprimak]

Chrome is the only browser I can reproduce this with

[carryel]

@lprimak It's too late. If you can still reproduce the issue and want to track it, could you provide the values ​​below when reproducing it?
If it only occurs in Chrome, it's likely a base64url issue.

HTTP Request's Header:

HTTP2-Settings: <base64url encoding of HTTP/2 SETTINGS payload>

[lprimak]

I guess the question is, where do I get those from? Is it from dev tools?
The way I reproduce it is to run Selenium tests, which close Chrome afterwards.
I guess I need to figure out a way to keep the browser open :)
Let me know if I am on the right track.

[carryel]

It would be nice to be able to view request headers through Chrome DevTools. If the browser is closed and you can't view them, you could capture network traffic with tools like Wireshark. If you could just find the value of the HTTP2-Settings header, I think this will be a great help in analyzing this problem.

If it only happens in Chrome and works fine in other browsers, it might be a good idea to compare the different HTTP2-Settings values.

[lprimak]

Ah, I got wireshark. Will try it, thanks