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

Document HTTP/2 compat #204

Closed
michael-o opened this issue Mar 25, 2019 · 4 comments
Closed

Document HTTP/2 compat #204

michael-o opened this issue Mar 25, 2019 · 4 comments

Comments

@michael-o
Copy link
Contributor

Hey there, I have configured Apache for Protocols h2 http/1.1 and like to know whether due to multiplexing streams it is still safe to use GssapiConnectionBound with HTTP/2. Moreover, the docs say "It incurs overhead, so leaving it off is recommended." What overhead? Checking connection notes for a principal is overhead if this gives more performance on persistent connections?

@simo5
Copy link
Contributor

simo5 commented Mar 25, 2019

If all streams come from the same user it will be safe, if it is used behind a proxy that may interleave different user requests, then definitely not safe.
The overhead is that we hang GSSAPI memory off the connection, so it may lead to additional memory usage for the life of a connection, and may add up if there are many connections.

In general GssapiConnectionBound is really only needed if you are performing NTLMSSP authentication (or another mechanism that performs more than 1 server roundtrip), for krb5 it is not necessary. We use cookies to avoid the need for multiple authentication at each roundtrip.

@simo5 simo5 closed this as completed Mar 25, 2019
@michael-o
Copy link
Contributor Author

michael-o commented Mar 25, 2019

The cookies are only available if the client supports them (e.g., browsers). Consider libserf accessing HTTPd, there is no cookie support

@simo5
Copy link
Contributor

simo5 commented Mar 25, 2019 via email

@michael-o
Copy link
Contributor Author

Alright, libserf does that in all gory details.

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

No branches or pull requests

2 participants