0
Fork 0
mirror of https://github.com/ninenines/cowboy.git synced 2025-07-14 12:20:24 +00:00

Note that we won't implement the HTTP/2 PRIORITY mechanism

This commit is contained in:
Loïc Hoguin 2023-12-07 16:45:30 +01:00
parent 6bc6100bbd
commit 0ce9696e5e
No known key found for this signature in database
GPG key ID: 8A9DF795F6FED764

View file

@ -12,6 +12,12 @@
%% ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF %% ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF
%% OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. %% OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE.
%% Note that Cowboy does not implement the PRIORITY mechanism.
%% Everyone has been moving away from it and it is widely seen
%% as a failure. Setting priorities has been counter productive
%% with regards to performance. Clients have been moving away
%% from the mechanism.
-module(rfc7540_SUITE). -module(rfc7540_SUITE).
-compile(export_all). -compile(export_all).
-compile(nowarn_export_all). -compile(nowarn_export_all).
@ -483,14 +489,6 @@ http_upgrade_client_preface_settings_ack_timeout(Config) ->
%% important, an OPTIONS request can be used to perform the upgrade to %% important, an OPTIONS request can be used to perform the upgrade to
%% HTTP/2, at the cost of an additional round trip. %% HTTP/2, at the cost of an additional round trip.
%% @todo If we ever handle priority, we need to check that the initial
%% HTTP/1.1 request has default priority. The relevant RFC quote is:
%%
%% 3.2
%% The HTTP/1.1 request that is sent prior to upgrade is assigned a
%% stream identifier of 1 (see Section 5.1.1) with default priority
%% values (Section 5.3.5).
http_upgrade_response(Config) -> http_upgrade_response(Config) ->
doc("A response must be sent to the initial HTTP/1.1 request " doc("A response must be sent to the initial HTTP/1.1 request "
"after switching to HTTP/2. The response must use " "after switching to HTTP/2. The response must use "