When creating a redirects.json I found a couple of irritating issues after migrating from another platform.
- The other platform uses case-insensitive urls… Ghost redirect.json is case sensitive.
- The other platforms allows url-encoded values in the url. It looks like redirect.json uses the encoded url, but it’s not clear which encoding it uses.
In my eyes it would be better when:
- Ghost would use the url-decoded url for redirect matching, at least that would give me one canonical version to work with. Now I can’t figure out what my exact url is.
- Ghost would allow the specification of regex modifiers like case-insensitive