News for hackers. Stuff that matters.
Re:Slack account takeovers using HTTP Request Smuggling by tialaramex on Friday March 13, 2020 @04:41PM (#22570723)
If you don't implement an encoding you should obey the HTTP/1.1 standard and "return 501 (Unimplemented), and close the connection". In your case even though not implementing chunked encoding is prohibited, this drop through would save you.

Valid means what the standard says it means. What you don't know can hurt you.

However, if modifying your backend code is hard, you can apparently tell nginx that you don't do chunked encoding and it will sort out the 501 on your behalf. I have not tried this and YMMV.

Re:Slack account takeovers using HTTP Request Smuggling by jackewiehose on Friday March 13, 2020 @05:00PM (#22570852)
I completly agree and I'm sure nginx is doing it right by following the specification but isn't this a bug in the specification? Why should there be a content-length but then a chunked body.

And if this is a bug in the specification, shouldn't nginx fix it to help us backend-fools?