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

Poor handling of HTTP error codes #903

Closed
krizhanovsky opened this issue Feb 5, 2018 · 0 comments
Closed

Poor handling of HTTP error codes #903

krizhanovsky opened this issue Feb 5, 2018 · 0 comments
Assignees
Labels

Comments

@krizhanovsky
Copy link
Contributor

krizhanovsky commented Feb 5, 2018

Use configuration from https://github.com/tempesta-tech/tempesta/wiki/Web-security#dns-rebinding and send a request like:

$ strace -s512 wget http://192.168.100.4/

(no Host header). In the strace output you'll see

HTTP/1.1 502 Bad Gateway\r\n
Date: Mon, 05 Feb 2018 10:09:34 GMT\r\n
Content-Length: 0\r\n
Connection: keep-alive\r\n\r\n

, no Server header, which is very wished. Moreover, Tempesta FW doesn't log anything in dmesg - all HTTP error responses must be logged with net ratelimiting.

@krizhanovsky krizhanovsky added this to the 0.6 KTLS milestone Feb 5, 2018
aleksostapenko added a commit that referenced this issue Mar 19, 2018
Fix #903: add logging for all error responses.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants