yeah i fully agree it's confusing !

i assumed Vitor meant a HTTP redirect  (which never works with NIP-05) when he wrote that but you could be right

i don't know which HTTP server you're using, so can't tell you exactly how to do it, but i think the right behavior to configure would be make it so that NAME argument from "https://minestr.app/.well-known/nostr.json?name=<NAME>"  (or alternatively, the entire URL) is lower-cased before using it to find the specific per-user file (as the file system will be case sensitive).

that would make https://minestr.app/.well-known/nostr.json?name=Chris return the same as https://minestr.app/.well-known/nostr.json?name=CHRIS and https://minestr.app/.well-known/nostr.json?name=chris, and make the verification work in all software. 

That the JSON name key in the returned document is lowercase "chris" is ok; NIP-05 is sufficiently clear that clients need to do that comparison case-insensitively, which is why Beareatta's works