Skip to content

HTTP 2? #332

@m-mohr

Description

@m-mohr

Section 8.1. "HTTP 1.1" states (highlights by me):

The standards used for Web APIs are built on the HTTP protocol. Therefore, conformance with HTTP or a closely related protocol is required.

This sounds like there's a door open for e.g. HTTP 2, but then the requirement disallows it:

OGC Web APIs SHALL conform to HTTP 1.1.

A couple of questions occur:

  • What is a closely related protocol? And why is it mentioned this way, if only HTTP 1.1 (+ over TLS) is supported anyway?
  • Why restrict to 1.1? This doesn't seem very future-proof. 2.0 at least seems pretty compatible to 1.1.

Metadata

Metadata

Assignees

No one assigned

    Labels

    Part 1Applicable to Part 1 Core

    Type

    No type

    Projects

    Status

    Backlog

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions