• Hi. I noticed our client uses /MechanicsburgSignature as a vanity short cut for some online needs. I added that as a 301, and it redirects fine BUT only if I have the “M” and “S” capitalized. If I try lower case letters, it fails. I know I can add another 301 redirect, but I am trying to avoid that as they may create many ones. Is there a setting we can use to not make it case-sensitive?

Viewing 4 replies - 1 through 4 (of 4 total)
  • I think there’s more than one way to do that, but one options is:
    – enable the Regex chechbox
    – edit the source URL to instead be /[Mm]echanicsburg[Ss]ignature

    That syntax means it will accept “any one of the characters within the square brackets”.

    Thread Starter icommllc

    (@icommllc)

    Thanks. Do you know of a way to do it automatically for all 301s? We are rebuilding a site and I need to do this for many entries.

    Sorry, I’m not aware of any “global” way to set it to be case insensitive – as far as I know you’ll have to edit every redirect.

    For an individual Source, surround it in delimiters and then trail it with the letter “i”. This makes the entire regex case-INsensitive. Example:
    {some regex here}i
    As to doing that with all of your sources, a mass change would need to be done with code or SQL, and a bit of thought as to whether you really want to do that.

    As to doing it through the UI, that would require a code change to the plugin from the author or a contributor.

Viewing 4 replies - 1 through 4 (of 4 total)
  • The topic ‘case sensitive?’ is closed to new replies.