You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Apr 26, 2023. It is now read-only.
Very basic testing with HTTP/2.0 server seems to work. However, there's a number of things that basic investigation highlighted or needs more investigation. Here's some initial notes:
When proxy hosted on HTTP/2.0:
HTTP/2 does away with the ‘reason phrase’. In HTTP/1.1 it was possible for servers to submit a human readable reason along with the status code, such as HTTP/1.1 404 Can't find it anywhere!. Or HTTP/1.1 200 I like pebbles, but in HTTP/2 this is removed. The proxies return these "reason phrases".
When HTTP/1.1 hosted proxy connects to HTTP/2.0 server:
HTTP/2.0 use lower-case headers (and with less white-space). HTTP/1.1 headers are supposed to be case-insensitive.
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. If you need additional assistance please contact Esri Technical Support. Thank you for your contributions.
Very basic testing with HTTP/2.0 server seems to work. However, there's a number of things that basic investigation highlighted or needs more investigation. Here's some initial notes:
When proxy hosted on HTTP/2.0:
When HTTP/1.1 hosted proxy connects to HTTP/2.0 server:
Ref:
https://http2.github.io/http2-spec/
https://evertpot.com/http-2-finalized/
The text was updated successfully, but these errors were encountered: