Your message dated Tue, 24 Dec 2013 14:12:23 +0100
with message-id <[email protected]>
and subject line [lighttpd] Handle nicely files with too long names
has caused the Debian Bug report #663259,
regarding [lighttpd] Handle nicely files with too long names
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)


-- 
663259: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=663259
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: lighttpd
Version: 1.4.30-1
Severity: normal
Tags: patch upstream forwarded-upstream

Hi.

Please apply the following trivial patch.
It changes current behavior nicely handling cases where requested files
have names too long, instead of throwing HTTP 500 Error (Internal Server
Error).

It's important to remark that this is a proper behavior. Other httpd's
out there also throw 4xx errors in this cases too, like Apache (403) and
nginx (404).

Find upstream report here[1].


Please consider applying it.



Cheers,

Dererk


ref:

1. http://redmine.lighttpd.net/issues/2396

-- 
BOFH excuse #295:
The Token fell out of the ring. Call us when you find it.

Author: Ulises Vitulli <[email protected]>
Description: Nicely handle files with names too long to be read throwing a 404.
Bug: http://redmine.lighttpd.net/issues/2396 

--- lighttpd-1.4.30.orig/src/response.c
+++ lighttpd-1.4.30/src/response.c
@@ -611,6 +611,8 @@ handler_t http_response_prepare(server *
 
                                buffer_reset(con->physical.path);
                                return HANDLER_FINISHED;
+                       case ENAMETOOLONG:
+                       /* file name to be read was too long. Unable to be 
read, throw a 404 */
                        case ENOENT:
                                con->http_status = 404;
 

Attachment: signature.asc
Description: OpenPGP digital signature


--- End Message ---
--- Begin Message ---
Hi,

I'm closing this bug as it was merged upstream and applied in 1.4.32
which we uploaded a while ago.


-- 
with kind regards,
Arno Töll
IRC: daemonkeeper on Freenode/OFTC
GnuPG Key-ID: 0x9D80F36D

Attachment: signature.asc
Description: OpenPGP digital signature


--- End Message ---

Reply via email to