Re: location ~* .(a|b|c)$ {} caused an error

2017-12-04 Thread Sophie Loewenthal
Oh. the closing } It’s been a long day <:-I > On 4 Dec 2017, at 18:57, Ian Hobson wrote: > > Hi Sophie, > > On 04/12/2017 16:49, Sophie Loewenthal wrote: >> Hi, >> When I put this location block for case insensitive matching into the vhost >> produced an error. >> nginx: [emerg] location

Re: location ~* .(a|b|c)$ {} caused an error

2017-12-04 Thread Ian Hobson
Hi Sophie, On 04/12/2017 16:49, Sophie Loewenthal wrote: Hi, When I put this location block for case insensitive matching into the vhost produced an error. nginx: [emerg] location "/" is outside location ".(jpg|jpeg|png|gif|ico|css|js)$" in /etc/nginx/sites-enabled/example.conf:13 My vhost

location ~* .(a|b|c)$ {} caused an error

2017-12-04 Thread Sophie Loewenthal
Hi, When I put this location block for case insensitive matching into the vhost produced an error. nginx: [emerg] location "/" is outside location ".(jpg|jpeg|png|gif|ico|css|js)$" in /etc/nginx/sites-enabled/example.conf:13 My vhost has this: server { … location ~* .(jpg|jpeg|png

Re: How to control the total requests in Ngnix

2017-12-04 Thread Peter Booth
I’ve used the equivalent of nodelay with a rate of 2000 req/sec per IP when a retail website was being attacked by hackers. This was in combination with microcaching and CDN to protect the back end and endure the site could continue to function normally. Sent from my iPhone > On Dec 4, 2017, a