Hi John, > It is possible to get nginx to match catch insensitively if you need > to. You have to use a case-insensitive regex match.
Yes, though in Terry's case he has Unix path names that are case sensitive, and URL paths that are too, given URLs were designed on Unix, so he shouldn't introduce ambiguity to cater for those that can't type. :-) If Audio_Guide is hard to type that's because it's not the more normal audio-guide. Terry, are you putting QR codes about for mobiles to open the URL? You could have a Wimborne Minster tower. https://research.swtch.com/qart > nginx location selection algorithm is a little hard to grok at first The key thing I found, especially compared to Apache, is the linear order of rules in the file is not the order of execution. Instead, they're sorted first by type, and then file order. It can help to order them this way in the file. Cheers, Ralph. -- Next meeting: Bournemouth, Tuesday, 2017-03-07 20:00 Meets, Mailing list, IRC, LinkedIn, ... http://dorset.lug.org.uk/ New thread: mailto:[email protected] / CHECK IF YOU'RE REPLYING Reporting bugs well: http://goo.gl/4Xue / TO THE LIST OR THE AUTHOR
