Claude Brisson

@michael-o curl example: $ curl --http2 -Nv "https://some.http2.url/" * Trying 127.0.0.1:8833... * TCP_NODELAY set * Connected to some.http2.url (127.0.0.1) port 8833 (#0) > GET / HTTP/1.1 > Host: some.http2.url:8833 >...

Of course, you will need to actually *add* the faulty header to the response to see this error.

@markt-asf This happens for instance in SSE components (tomcat does *not* provide such components), or more generally in *any* J2EE filters or servlets, coded before HTTP/2.0, which want to ensure...

I see. But at that point, you do not know who set up the header, so the stack trace won't be informative.

> Can you retry with a vanilla Tomcat and the most recent curl? I've spent enough time digging for this bug (to end up finding it in a SSE dependency),...

> Could you expand the SSE acronym please. I want to make sure I understand you correctly. [Server-Side Events](https://html.spec.whatwg.org/multipage/server-sent-events.html) > Code format issues are opening braces `{` should not be...

@rmaucher The spec authors justify themselves of this strict policy by saying that otherwise it's a vector of attack. I don't know the whereabouts, here. About where to put the...

There are a lot of good ideas in your proposal, but I don't understand why you would want to rely on annotations on the target classes. You say that your...

@r4zzz4k Thanks for those clarifications. Is this KEEP still pertinent, then?

To quote Michael on the dev list: > This seems to be a very specific resource loader and shall be hosted outside of core. This could be in a contrib...