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 was archived by the owner on Apr 22, 2023. It is now read-only.
I know http spec says headers is case-insensitive, but I'm implementing a transparent proxy.
And as far as I know, some headers should not be modified by proxy.
Some features of the HTTP/1.1 protocol, such as Digest
Authentication, depend on the value of certain end-to-end headers. A
transparent proxy SHOULD NOT modify an end-to-end header unless the
definition of that header requires or specifically allows that.
It should be nice if I could retrieve original headers using http module because it does lots of hard work over sockets.
The text was updated successfully, but these errors were encountered:
I know http spec says headers is case-insensitive, but I'm implementing a transparent proxy.
And as far as I know, some headers should not be modified by proxy.
http://tools.ietf.org/html/rfc2616
13.5.2 Non-modifiable Headers
Some features of the HTTP/1.1 protocol, such as Digest
Authentication, depend on the value of certain end-to-end headers. A
transparent proxy SHOULD NOT modify an end-to-end header unless the
definition of that header requires or specifically allows that.
It should be nice if I could retrieve original headers using http module because it does lots of hard work over sockets.
The text was updated successfully, but these errors were encountered: