New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

HTTP 2? #332

Open

m-mohr opened this issue Jun 1, 2023 · 0 comments

Labels

Part 1

m-mohr commented Jun 1, 2023

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.

jerstlouis added the Part 1 label

github-project-automation bot added this to OGC API - Common - Part 1: Core

github-project-automation bot moved this to Backlog in OGC API - Common - Part 1: Core

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment