requests like these are hitting my server, and i want to catch these
requests, and return ‘not found’ from nginx. i dont want it to hit my
fastcgi backend.
[13/Aug/2010:19:39:26 -0700] “POST /%5C%22http:%5C/%5C/ photos-b.ak.fbcdn.net%5C/photos-ak-snc1%5C/v43%5C/64%5C/68931197560%5C/app_2_68931197560_3211.gif%5C%22
HTTP/1.1” 404 103 “-” “Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5;
en-US; rv:1.9.2.8) Gecko/20100722 Firefox/3.6.8” 0.087 US
how do i match requests with url starting like this:
and take care of them from nginx, and not hit the fastcgi backend.
What does the referer look like? This request looks like it is generated
by
some script and you probably want to find out what the source for them
is.
Are you sure that it’s not one of your own scripts/php pages that
generates
these?
On Sat, Aug 14, 2010 at 12:01 PM, Edho P Arief [email protected]
wrote:
fastcgi backend.
how do i match requests with url starting like this:
rewrite ^/(.*) www.XXX.com permanent;
}
it does not catch it. it is still hitting my fastcgi backend
put it in the topmost of your server block.
yes i have it in the top most position in server block. all other
location
sections are below this and it still does not catch it. it is going to
the
location that matches the last block
location / {
On Sat, Aug 14, 2010 at 12:14:46PM -0700, kevin wrote:
requests like these are hitting my server, and i want to catch these
location /\"http:\/\/ {
yes i have it in the top most position in server block. all other location
sections are below this and it still does not catch it. it is going to the
location that matches the last block
location / {
Sorry, the slashes should be escaped, this is working configuration: