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 <jeff.dyke@gmail.com> wrote:

> 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 find
> more that are after this directory. When i was at an image heavy start up,
> we had every one imaginable.
>
> Best,
> Jeff
>
> On Wed, Jun 21, 2017 at 3:40 PM, lists@lazygranch.com <
> lists@lazygranch.com> wrote:
>
>> 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.GoogleMobile)) {
>> return 403;
>> }
>> ---------
>>
>> 403 107.2.5.162 - - [21/Jun/2017:07:21:08 +0000] "GET /images/photo.jpg
>> HTTP/1.1" 140 "-" "com.google.GoogleMobile/28.0.0 iPad/10.3.2
>> hw/iPad6_7" "-"
>>
>>
>>
>> _______________________________________________
>> nginx mailing list
>> nginx@nginx.org
>> http://mailman.nginx.org/mailman/listinfo/nginx
>>
>
>
> _______________________________________________
> nginx mailing list
> nginx@nginx.org
> http://mailman.nginx.org/mailman/listinfo/nginx
>
_______________________________________________
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx