Ah but I want Google to look, but just return links to pages, not images. There all those hits that pretend to be Google, because hey, why not. ;-) I block a large number of bots simply by the firewall. I started
U-27, which is a plane recently in the
> news. You get a lot of SU-35s. Is this really rocket science? I assume Google
> has no trust in image tags. But many images have SU-35 in text, which could
> be read using openCV, as is done with openALPR. But I'm rambling.
>
>
The IP addresses from the Google app aren't those of Google. They are ISPs generally. What bugs me is a fair number of these IP addresses never read my web pages. Easy enough to see from access.log. They just look
I ended up digging a bit more and found that I believe Richard to be
correct in both cases. I would check the ips and see who they belong to,
you may just be hurting your mobile users.
On Thu, Jun 22, 2017 at 11:03 AM, Richard Stanway wrote:
> That user agent doesn't belong to a Google crawle
That user agent doesn't belong to a Google crawler - they are end-user
requests from the Google App (mobile application). I'm not sure what the
motivation is for blocking them but I wouldn't consider it malicious /
unwanted traffic.
On Thu, Jun 22, 2017 at 4:47 PM, Jeff Dyke wrote:
> I'm glad yo
I'm glad you found the solution, but being a Google crawler, it would
likely respect a robots.txt file with Disallow: images/*, which if it
worked would allow you to remove an if clause from being evaluated on every
page load.
You may have already tried it. But i have a feeling you'll start to fi
I'm sending 403 responses now, so I screwed up by mistaking the fields
in the logs. I'm going back to lurking mode again with my tail
shamefully between my legs.
This code in the image location section will block the google app:
if ($http_user_agent ~* (com.google.GoogleMobi
gt; Sent: Tuesday, June 20, 2017 6:47 PM
> To: nginx@nginx.org
> Reply To: nginx@nginx.org
> Subject: Re: block google app
>
> Well what is your log format then? We can't possibly help you if we
> don't have the necessary info ;)
>
> Do you want to block based on ht
e
From: Robert Paprocki
Sent: Tuesday, June 20, 2017 6:47 PM
To: nginx@nginx.org
Reply To: nginx@nginx.org
Subject: Re: block google app
Well what is your log format then? We can't possibly help you if we don't have
the necessary info ;)
Do you want to block based on http referer? Or us
Well what is your log format then? We can't possibly help you if we don't have
the necessary info ;)
Do you want to block based on http referer? Or user agent string? Or something
else entirely? The config snippet you posted indicates you are trying to block
by referer. If you want to block a r
I think the ipad is the useragent. I wiped out that access.log, but
here is a fresh one showing a browser (user agent) in the proper field.
200 76.20.227.211 - - [21/Jun/2017:00:48:45 +] "GET /images/photo.jpg
HTTP/1.1" 91223 "http://www.mydomain.com/page.html"; "Mozilla/5.0 (Linux;
Android
Do you mean $http_user_agent?
> On Jun 20, 2017, at 17:36, "li...@lazygranch.com"
> wrote:
>
> I would like to block the google app from directly downloading images.
>
> access.log:
>
> 200 186.155.157.9 - - [20/Jun/2017:00:35:47 +] "GET /images/photo.jpg
> HTTP/1.1" 334052 "-" "com.goo
I would like to block the google app from directly downloading images.
access.log:
200 186.155.157.9 - - [20/Jun/2017:00:35:47 +] "GET /images/photo.jpg
HTTP/1.1" 334052 "-" "com.google.GoogleMobile/28.0.0 iPad/9.3.5 hw/iPad2_5" "-"
My nginx code in the images location:
if ($http_referer
13 matches
Mail list logo
