[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[lwip-devel] [bug #56290] HTTPD 404/400/501 URI detection causes wrong h

From: Josh
Subject: [lwip-devel] [bug #56290] HTTPD 404/400/501 URI detection causes wrong headers to be sent
Date: Mon, 13 May 2019 13:56:03 -0400 (EDT)
User-agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/74.0.3729.131 Safari/537.36

Follow-up Comment #2, bug #56290 (project lwip):


What about "4007fd3aade94aad64c82a07c74002aa.jpg"? This is just as possible as
the previous example "bad7fd3aade94aad64c82a07c74002aa.jpg". Each has 400 in
the file name, one just happens to have it at the beginning. I think any fix
should eliminate absolutely any possibility of a file other than the actual
true error file serving up the wrong status headers.

If a defined starting path is used, it seems like it would be necessary to
also check the files explicitly, instead of "URI starts with /404". That is,
the defined path + .html, .htm, or .shtml. This would fix it fully (at some

What do you think?


Reply to this item at:


  Message sent via Savannah

reply via email to

[Prev in Thread] Current Thread [Next in Thread]