PathPrefix and PathPrefixExclude should not be case sensitive. This leads to some bugs and weird behavior (see "Steps to reproduce").

Note that in 3.10 and 4.0 case sensitivity was introduced for URL aliases stored in database but not for real-life URLs used by site vistitors. (Example: an article called "About Us" gets an auto-generated alias "About-Us" stored in the database but on the actual site you can use "www.example.com/about-us", "www.example.com/About-us", "www.example.com/ABOUT-US" and so on.)

Steps to reproduce

I have the following content structure:

products (folder)
-- sveta (folder)
---- my (article)

Added "PathPrefix=products/sveta" for a public siteaccess.

If I enter "http://example.com/my" as a URL, everything is correct (the "my" article is displayed and the "products/sveta" part is not shown in the URL).

However, if I use uppercase letters, PathPrefix doesn't work as expected:

1. I renamed the "sveta" folder to "Sveta" without changing the PathPrefix setting.

If I enter "http://example.com/my", the system says "Module not found" while the URL in the address bar is transformed to "http://example.com/<my_siteaccess>/products/Sveta/my".

It only works correctly if I specify "PathPrefix=products/Sveta" with capital S.

2. Renamed the article from "my" to "My".

If I enter "http://example.com/My" with capital M, everything is correct.

If I enter "http://example.com/my", the article is shown but the URL in the address bar changes to
http://example.com/<my_siteaccess>/products/Sveta/My

3. Full URLs for visitors siuddenly became case-sensitive. They only work if the prefix part in the full URL is entered exactly the same as the PathPrefix setting.