Uploaded image for project: 'WildFly'
  1. WildFly
  2. WFLY-5364

HTTP2 stream ID is not checked for some frame types

    XMLWordPrintable

Details

    Description

      According to RFC7540 frame types DATA, PRIORITY and HEADERS are associated with particular data stream, therefore if its stream id is 0 this should be processed as PROTOCOL_ERROR.

      Similarly frames of types GOAWAY and SETTINGS must not be associated with particular stream id other than 0, if so then PROTOCOL_ERROR should be raised.

      With current implementation this requirement is not checked causing discrepation against RFC specification.

      Attachments

        Issue Links

          Activity

            People

              sdouglas1@redhat.com Stuart Douglas
              jstourac@redhat.com Jan Stourac
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: