Skip to content
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

Handle :authority pseudo-header #104

Merged
merged 1 commit into from
Jun 10, 2020
Merged

Conversation

Altai-man
Copy link
Member

This unblocks obtaining of Host when using HTTP/2 Cro server.

Related to https://stackoverflow.com/questions/62253651/how-to-get-the-host-or-authority-header-in-cro-when-using-http-2

acw++ for noticing and reporting.

This unblocks obtaining of Host when using HTTP/2 Cro server.
@Altai-man Altai-man requested a review from jnthn June 10, 2020 18:45
@jnthn
Copy link
Member

jnthn commented Jun 10, 2020

Seems like the dual of ddd7ff1, which I neglected to think of when I did that. Thanks!

@jnthn jnthn merged commit 2574a3c into master Jun 10, 2020
@jnthn jnthn deleted the propagate-all-pseudo-headers branch June 10, 2020 19:32
@arjancwidlak
Copy link

Hi,

Thank you for picking this up! And explaining your steps on stackoverflow. I'm just getting acquainted with Cro.

I can confirm this works perfectly now using Chrome. Chrome sends the :authority header under HTTP/2.

My Mozilla Firefox (68.9.0esr (64-bit) on linux) however sends the Host header under HTTP/2 and this fix doesn't work for my firefox.

Kind regards,
Arjan.

@Altai-man
Copy link
Member Author

Hi. I will try to look at it soon. The firefox issue sounds rather odd to me, because I am not sure RFC allows something like that, but OTOH firefox devs must be far better than me in doing this stuff, so we want to be compatible.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants