I think you want to take this up with the thttpd developers. My personal opinion is that you should fix the client that's broken, not the server that does what it's told.
//art x <where.can.that.fish...@googlemail.com> writes: > To reproduce the problem, have a thttpd on port 12345 and compare > ftp http://localhost:12345/index.html > with > ftp http://localhost:12345//index.html > > The behaviour differs from httpd(8), and some clients trip over it. > > $ cat ports/www/thttpd/patches/patch-libthttpd_c > --- libhttpd.c.orig Mon Mar 30 08:54:18 2009 > +++ libhttpd.c Mon Mar 30 08:59:12 2009 > @@ -2024,6 +2024,8 @@ > httpd_realloc_str( > &hc->origfilename, &hc->maxorigfilename, strlen( hc->decodedurl ) ); > (void) strcpy( hc->origfilename, &hc->decodedurl[1] ); > + while ( hc->origfilename[0] == '/' ) > + ++hc->origfilename; > /* Special case for top-level URL. */ > if ( hc->origfilename[0] == '\0' ) > (void) strcpy( hc->origfilename, "." ); > $
