-
Notifications
You must be signed in to change notification settings - Fork 304
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
OPTIONS response has invalid blank header with no value #217
Comments
Thanks for reporting this, I didn't see it yesterday when I ran it with an older version of Webdis but I can reproduce it on the latest. This is likely a regression from #205. /cc @jessie-murray |
@jessie-murray I've tracked it down with This is due to the header replacement code in Lines 100 to 108 in dc9d1b6
but later still increments the header count: Line 117 in dc9d1b6
It needs to avoid this increment if no new value was added. For the case of |
Fix for nicolasff#217, a regression added in nicolasff#205. The "header_count" field was incremented even when we overwrote a header entry, which caused Webdis to send a header with no name and no value.
I discussed the issue on the Fly help forum regarding the OPTIONS request responding with no CORS headers in #216. Fly's HTTP proxy is returning 502 because the OPTIONS response from Webdis has a blank
:
header with no name or value.See two lines above last line:
https://community.fly.io/t/http-handler-502-errors-on-options-request/4160/5?u=ewired
The text was updated successfully, but these errors were encountered: