E.B.
May 20, 2015 07:50PM
> > 2^4 = all 16 combinations. Hopefully the 'test' sting is only 4
> > characters
> > long...
> >
> > Case-insensitiveness is no-trivial check, and if needed PCRE are here
> > for
> > that through regex locations.
> > What is wrong with them already??
>
> At assembly level alot, +-20 bytes including an if or alot more when it has
> to go through pcre.

Exactly. PCRE engine adds overhead and is slower than just case
folding.

PLUS the Nginx location directive adds more overhead I'd like to avoid
because of its processing order. I know the exact text of what I want to
match, so = is the best choice. But I can't control the case of what clients
use.

But answers seem to indicate Nginx has no such feature.

_______________________________________________
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
Subject Author Posted

Case insensitive exact location match?

E.B. May 18, 2015 11:08PM

Re: Case insensitive exact location match?

J.J J May 20, 2015 04:48AM

Re: Case insensitive exact location match?

itpp2012 May 20, 2015 06:03AM

Re: Case insensitive exact location match?

B.R. May 20, 2015 06:38AM

Re: Case insensitive exact location match?

itpp2012 May 20, 2015 07:03AM

Re: Case insensitive exact location match?

J.J J May 23, 2015 08:48PM

Re: Case insensitive exact location match?

E.B. May 20, 2015 07:50PM



Sorry, only registered users may post in this forum.

Click here to login

Online Users

Guests: 165
Record Number of Users: 8 on April 13, 2023
Record Number of Guests: 421 on December 02, 2018
Powered by nginx      Powered by FreeBSD      PHP Powered      Powered by MariaDB      ipv6 ready