Bug #1589
server.force-lowercase-filenames doesn't work inside userdir's
0%
Description
Hi,
I run lighttpd 1.4.19 on Linux on top of a case-insensitive filesystem (JFS with OS/2 compatibility enabled). I noticed that while lighty forces lower case filenames for files within the server.document-root, it doesn't for files in a userdir.
Example:
The original filename is test.php (works):
http://andersman.org/test.php
http://andersman.org/test.PHP
The original filename is test.php (shows sources !!):
http://andersman.org/~anders/test.php
http://andersman.org/~anders/test.PHP
-- anders1
Associated revisions
History
Updated by kaank over 10 years ago
Added a patch that should solve the problem by using buffer_to_lower before assigning the path to physical.path - first patch and first real attempt at solving a lighty bug so if I've overlooked something let me know so I can correct it with this and future patches.
Updated by stbuehler about 10 years ago
- Status changed from New to Fixed
- Resolution set to fixed
"Fixed" in r2283 - but i wouldn't use a case-insensitive filesystem if i needed a secure webserver; i guess there are more problems in that area than we will ever find.
I didn't use your patch as there is more than lowercase on windows.
Also available in: Atom
Fix bug with case-insensitive filenames in mod_userdir (#1589)
git-svn-id: svn://svn.lighttpd.net/lighttpd/branches/lighttpd-1.4.x@2283 152afb58-edef-0310-8abb-c4023f1b3aa9