•
•
•
•
What is DaniWeb IT Discussion Community?
You're currently browsing the Linux Servers and Apache section within the Tech Talk category of DaniWeb, a massive community of 427,933 software developers, web developers, Internet marketers, and tech gurus who are all enthusiastic about making contacts, networking, and learning from each other. In fact, there are 2,908 IT professionals currently interacting right now! Registration is free, only takes a minute and lets you enjoy all of the interactive features of the site.
Please support our Linux Servers and Apache advertiser: Programming Forums
Views: 546 | Replies: 0
![]() |
•
•
Join Date: Jul 2008
Posts: 2
Reputation:
Rep Power: 0
Solved Threads: 0
Hello,
I would like to start a discussion about the pros and cons of making apache (on linux) deal eloquently with capital letters in a URL.
I had a user submit a trouble ticket saying that our web server must be broken because http://example.com/example.html works but http://mysite.com/EXAMPLE.html does not.
Obviously, after some google searches, I found that this indeed is not the sign of a broken web server, that URI's are defined to be case-sensitive.
So I searched for some possible solutions to get around this. I found I could:
I talked to my sys admin to see what he thought about all this and he's not feeling it at all. He doesn't like the fact that there are probably some miscellaneous scenarios that would produce unpredictable results. He also thinks people shouldn't have to memorize URLs in the first place.
So, then I tried to find some good arguments I could possibly give my user supporting why I shouldn't "fix" this for him. Here are the ones I've found:
However, I know he's going to come back at me with a usability argument. But I really don't want to do something that my sys admin is uncomfortable with...even though he said ultimately it is up to me.
I'm curious to know other people's take on the situation.
......discuss.
I would like to start a discussion about the pros and cons of making apache (on linux) deal eloquently with capital letters in a URL.
I had a user submit a trouble ticket saying that our web server must be broken because http://example.com/example.html works but http://mysite.com/EXAMPLE.html does not.
Obviously, after some google searches, I found that this indeed is not the sign of a broken web server, that URI's are defined to be case-sensitive.
So I searched for some possible solutions to get around this. I found I could:
- Install mod_speling
- Use mod_rewrite to convert all urls to lowercase
- Use a script in the 404 error page to detect a capital letter in the url, and if there is, suggest the lowercase equivalent.
I talked to my sys admin to see what he thought about all this and he's not feeling it at all. He doesn't like the fact that there are probably some miscellaneous scenarios that would produce unpredictable results. He also thinks people shouldn't have to memorize URLs in the first place.
So, then I tried to find some good arguments I could possibly give my user supporting why I shouldn't "fix" this for him. Here are the ones I've found:
- the URI specification itself says that URLs are case-sensitive and why mess with specifications?
- the two different urls will be cached separately by proxies, which could make things inefficient and result in the server taking more hits than it needs.
- my sys admin's argument that it could produce unexpected results in some situations.
However, I know he's going to come back at me with a usability argument. But I really don't want to do something that my sys admin is uncomfortable with...even though he said ultimately it is up to me.
I'm curious to know other people's take on the situation.
......discuss.
![]() |
•
•
•
•
•
•
•
•
DaniWeb Linux Servers and Apache Marketplace
•
•
•
•
Currently Active Users Viewing This Thread: 1 (0 members and 1 guests)
Other Threads in the Linux Servers and Apache Forum
- Previous Thread: disallow hidden directory access with httpd.conf
- Next Thread: Hiding Extensions


Linear Mode