You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@trafficserver.apache.org by "duke8253 (via GitHub)" <gi...@apache.org> on 2023/06/15 19:28:49 UTC

[GitHub] [trafficserver] duke8253 commented on issue #9428: Prohibit a second SETTINGS frame

duke8253 commented on issue #9428:
URL: https://github.com/apache/trafficserver/issues/9428#issuecomment-1593609025

   While reading our code and the documentation, I noticed that we don't seem to enforce one control stream per connection?
   
   https://datatracker.ietf.org/doc/html/rfc9114#control-streams
   
   > Only one control stream per peer is permitted; receipt of a second stream claiming to be a control stream MUST be treated as a [connection error](https://datatracker.ietf.org/doc/html/rfc9114#errors) of type [H3_STREAM_CREATION_ERROR](https://datatracker.ietf.org/doc/html/rfc9114#H3_STREAM_CREATION_ERROR).
   
   
   Also maybe we should rename `_control_stream_dispatcher` to something else, since use it to handle `PUSH` streams too?
   
   https://github.com/apache/trafficserver/blob/a29574d2fd089b90f1b909aedbb67b8000f01711/proxy/http3/Http3App.cc#L211-L218


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: issues-unsubscribe@trafficserver.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org