case sensitivity

[eluser]theprodigy[/eluser]
For some reason, my controllers have become case sensitive.

Example: domain.tld/users != domain.tld/Users

I had to edit the URI protocol in config.php in order to get it to work at all. It is now set to REQUEST_URI. Is this because of the way that protocol handles requests?

I didn't seem to have an issue with this before.

Thanks

[eluser]überfuzz[/eluser]
If you like to compare strings with uppercase and lowercase you could use some of the core functions... strtolower() Just saying.

[eluser]theprodigy[/eluser]
I am not wanting to compare them. My controller names used to not be case sensitive, but now they are. And it seems to be based on the file name. I usually lowercase the file name, uppercase the class name (users.php, class Users). I'm not sure why they are case sensitive now. I'm trying to set it back to NOT being case sensitive so that whatever is in the url is ok, as long as a controller with that name exists regardless of case.

[eluser]überfuzz[/eluser]
Ok, I've always used uppercase on the first letter of a class and lowercased the entire file name. Anyhow, read the guide for more info: user_guide/general/controllers

[eluser]jedd[/eluser]
[quote author="theprodigy" date="1252893886"]
My controller names used to not be case sensitive, but now they are.
[/quote]

So - what changed?

[eluser]theprodigy[/eluser]
not sure. It's a new project. My other projects seem to be fine, but on this one, they are case sensitive.

I have 2 system directories (one for 1.7.1 and one for 1.7.2). I at first was pointing to system172, but thought that the new one was affecting it somehow, and switched it to the original system folder. But that didn't fix it any. Other than that, the only differences are on my computer, but not on the server (server is same as other projects, my development machine is currently my Windows Vista laptop instead of my Linux tower.

[eluser]theprodigy[/eluser]
my apologies, I just realized that my previous projects are case sensitive. I never noticed it before because I never came across a time when it threw an error. It just seemed to always work. Oh well, thanks anyway