Hi,
Seeking technical support referencing sites moved from a hosting company using Apache servers, to another using LiteSpeed servers.
To be precise, we need to continue having our files, folders and URLS function as case ‘insensitive’
In our .htaccess files in the root folders, on the previous host on Apache servers, the following code worked - recognizing any uppercase characters as lowercase, within URLs, and for all types of files.
There are now seen 404 errors. Respective URLS do not work on the sites now at the new host using LiteSpeed servers. The same is of course happening for folders and other file types - .JPG to .jpg or .HTM to .htm or .DOC to .doc - any and all – or vice versa, where 404 errors are also generated.
To illustrate:
An example (not our actual site link) follows of such a scenario of an URL containing mixed-case characters, ‘typed’ or that would be reachable through a link when previously hosted on Apache servers:
Previously, site visitors would still reach the page at this [sample] link, while showing up in the browser address bar, all lowercase, as https://www.whenwetry.com/top/thisonetime.htm.
Now, if links are input in the browser directly – typed, for instance - all lowercase, like above – they display a 404 Error.
Also, working links and files are no longer ‘forced’ to lowercase either – they are showing up ‘mixed case’ in the browser if that is the original format.
So two situations to be rectified for our sites to function as they did when on Apache servers:
Do these include coding with the following parameters:
RewriteCond
RewriteRule
RewriteMap ?
Thanks so very much in advance.
Seeking technical support referencing sites moved from a hosting company using Apache servers, to another using LiteSpeed servers.
To be precise, we need to continue having our files, folders and URLS function as case ‘insensitive’
In our .htaccess files in the root folders, on the previous host on Apache servers, the following code worked - recognizing any uppercase characters as lowercase, within URLs, and for all types of files.
<IfModule mod_speling.c>
CheckCaseOnly On
CheckSpelling On
</IfModule>
There are now seen 404 errors. Respective URLS do not work on the sites now at the new host using LiteSpeed servers. The same is of course happening for folders and other file types - .JPG to .jpg or .HTM to .htm or .DOC to .doc - any and all – or vice versa, where 404 errors are also generated.
To illustrate:
An example (not our actual site link) follows of such a scenario of an URL containing mixed-case characters, ‘typed’ or that would be reachable through a link when previously hosted on Apache servers:
https://www.whenwetry.com/TOP/thisOneTime.htm - or the relative form contained within an .htm page or similar - ../TOP/thisOneTime.htm
Previously, site visitors would still reach the page at this [sample] link, while showing up in the browser address bar, all lowercase, as https://www.whenwetry.com/top/thisonetime.htm.
Now, if links are input in the browser directly – typed, for instance - all lowercase, like above – they display a 404 Error.
Also, working links and files are no longer ‘forced’ to lowercase either – they are showing up ‘mixed case’ in the browser if that is the original format.
So two situations to be rectified for our sites to function as they did when on Apache servers:
- How exactly to have case ‘insensitive’ enabled on our sites now on the LiteSpeed servers, so all content will work, regardless of what ‘case’ is contained - or as already exists on our sites?
- And subsequently, how to continue to ‘force’ lowercase in generated URLs in the address bar?
Do these include coding with the following parameters:
RewriteCond
RewriteRule
RewriteMap ?
Thanks so very much in advance.