-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
Handling of RFC7540 8.1.2.5 specification #189
Comments
Is my understanding correctly that you want a feature that transform the cookie headers in the old format to the new format when the system proxies the traffic to a HTTP/1.1 upstream? |
Hi! I did forget to specify, that this only needs to be done for HTTP/2 upstream. This can be either a feature or standard |
RFC7540 8.1.2.5 only requires this conversion to happen
But I do see that this could be an useful feature. On the other hand, many cloud APIs requires signed URLs, which means that any modification on the request headers could break these API traffic. So if we have such a feature it would be optional and default off. |
Yes I agree
Does mean only concatenating the cookie headers, if the context changes. Maybe a feature or flag could be useful to indicate a change of context in a proxy. And yes, the default should be off. |
Hi Team,
I would like pingora to follow the RFC7540 8.1.2.5 specification or at least a feature that would allow switching between the old and new specification.
This has become a problem, because a website I'm working on can't handle the old way of parsing cookie headers
The issue lies in the h2 crate. I have mentioned this to the maintainers but they have decided that
Hence why I'm requesting this feature
The text was updated successfully, but these errors were encountered: