-
Notifications
You must be signed in to change notification settings - Fork 26
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.
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
[gateway] Accept backends/entrypoints supporting only HTTP/2 #3105
Closed
abatista75 opened this issue
Jan 17, 2020
· 2 comments
· Fixed by gravitee-io/gravitee-definition#75, gravitee-io/gravitee-common#41, gravitee-io/gravitee-management-rest-api#1103, gravitee-io/gravitee-management-webui#1277 or gravitee-io/gravitee-gateway-api#56
Closed
[gateway] Accept backends/entrypoints supporting only HTTP/2 #3105
abatista75 opened this issue
Jan 17, 2020
· 2 comments
· Fixed by gravitee-io/gravitee-definition#75, gravitee-io/gravitee-common#41, gravitee-io/gravitee-management-rest-api#1103, gravitee-io/gravitee-management-webui#1277 or gravitee-io/gravitee-gateway-api#56
Labels
Milestone
Comments
abatista75
changed the title
Enable HTTP/2 at the entrypoint-level
Accept backends/entrypoints supporting only HTTP/2
Jan 17, 2020
Hi @adubreuiltk HTTP/2 (and gRPC) support will be provided in 3.0 |
Thanks!!! |
brasseld
changed the title
Accept backends/entrypoints supporting only HTTP/2
[gateway] Accept backends/entrypoints supporting only HTTP/2
Jun 23, 2020
brasseld
added a commit
to gravitee-io/gravitee-definition
that referenced
this issue
Jun 29, 2020
brasseld
added a commit
to gravitee-io/gravitee-common
that referenced
this issue
Jun 29, 2020
brasseld
added a commit
to gravitee-io/gravitee-management-rest-api
that referenced
this issue
Jun 29, 2020
brasseld
added a commit
to gravitee-io/gravitee-management-webui
that referenced
this issue
Jun 29, 2020
brasseld
added a commit
to gravitee-io/gravitee-gateway-api
that referenced
this issue
Jun 29, 2020
This was referenced Jun 29, 2020
brasseld
added a commit
to gravitee-io/gravitee-common
that referenced
this issue
Jul 1, 2020
brasseld
added a commit
to gravitee-io/gravitee-definition
that referenced
this issue
Jul 2, 2020
brasseld
added a commit
to gravitee-io/gravitee-management-webui
that referenced
this issue
Jul 2, 2020
aelamrani
pushed a commit
to gravitee-io/gravitee-api-management
that referenced
this issue
Jul 3, 2020
aelamrani
pushed a commit
to gravitee-io/gravitee-api-management
that referenced
this issue
Jul 3, 2020
aelamrani
pushed a commit
to gravitee-io/gravitee-gateway-api
that referenced
this issue
Jul 3, 2020
aelamrani
pushed a commit
to gravitee-io/gravitee-management-webui
that referenced
this issue
Jul 3, 2020
aelamrani
pushed a commit
to gravitee-io/gravitee-management-rest-api
that referenced
this issue
Jul 3, 2020
aelamrani
pushed a commit
to gravitee-io/gravitee-common
that referenced
this issue
Jul 3, 2020
aelamrani
pushed a commit
to gravitee-io/gravitee-definition
that referenced
this issue
Jul 3, 2020
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
If the backend only accepts HTTP/2, the connection fails with the error:
Expected Behavior
Gravitee should be able to connect to a backend using HTTP/1.1 or HTTP/2.
Current Behavior
If the backend only supports HTTP/2, then the API call fails.
Possible Solution
Either offer an option at the entrypoint-level to define the preferred HTTP version it both are supported by the backend, or apply an default rule (i.e. HTTP/2 with failover on HTTP/1.1)
Steps to Reproduce (for bugs)
Your Environment
The text was updated successfully, but these errors were encountered: