Hey there,
We dug into this further and will share our findings: what we automatically normalize are paths for files that exist in your deploy at your domain before any redirect rules apply, i.e. if you have a file at https://yoursite.com/HSAInfographic, we will normalize (force lowercase) that path to be https://yoursite.com/hsainfographic in the browser.
However, if have a redirect rule in your _redirects file or netlify.toml that says “redirect /HSAInfographic to /otherpath”, we will do exactly that- this is case-sensitive, and we will only redirect requests for /HSAInfographic (not /hsainfographic) to /otherpath.
Could you make redirect rules that account for the most common case usages? I.e.:
livelyme.com/individual-and-family-features/debit-card /otherpath 301
livelyme.com/individual-and-family-features/DEBIT-card /otherpath 301
livelyme.com/individual-and-family-features/debit-CARD /otherpath 301
etc