-
Notifications
You must be signed in to change notification settings - Fork 263
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
warp-tls strips out the Host request header #478
Comments
I'm not actually quite sure what's going on in warp-tls right now, @kazu-yamamoto would this be an easy thing for you to fix? |
Probably you cut and pasted a wrong example since it has a Host header. However, I confirmed that WAI apps don't receive Host headers with WarpTLS. This happens only with github code, not with released code. |
Never mind. This happens even with warp-tls 3.1.4. |
Fixed. @snoyberg If your problem has gone away with the commit above, please close this issue. |
Confirmed fixed, thanks! |
Just discovered this due to some buggy behavior in
yesod devel
, where URLs were misgenerated for TLS connections but generated correctly for non-TLS connections. Take as an example the following print of aRequest
value for a warp-tls connection:Note that while the
requestHeaderHost
field is populated, theHost
header itself does not appear in therequestHeaders
, in contrast with warp itself which populates both. This harms the situation, for example, when reverse proxying.The text was updated successfully, but these errors were encountered: