Support » Plugin: NIX Gravatar Cache » nginx requests flooding error logs

  • Hi, I’ve recently begun seeing some new lines flooding my error logs and I’m curious if it’s related to this plugin and if so, you have an idea for how I can mute or address them? This is from php logs running on Apache – we don’t have an Ngnix server running. Thanks for any help,

    
    < Date: Mon, 28 Nov 2016 21:11:23 GMT
    < Content-Type: image/jpeg
    < Content-Length: 5963
    < Connection: keep-alive
    < Last-Modified: Thu, 05 May 2016 10:34:30 GMT
    < Link: <https://www.gravatar.com/avatar/8252157200a6f9eccb545a4cbe6391d5?s=120&r=G>; rel="canonical"
    < Content-Disposition: inline; filename="8252157200a6f9eccb545a4cbe6391d5.jpeg"
    < Access-Control-Allow-Origin: *
    < X-nc: MISS ewr 3
    < Accept-Ranges: bytes
    < Expires: Mon, 28 Nov 2016 21:16:23 GMT
    < Cache-Control: max-age=300
    < Source-Age: 0
    <
    * Connection #1 to host www.gravatar.com left intact
    * Hostname was NOT found in DNS cache
    *   Trying 192.0.73.2...
    * Connected to www.gravatar.com (192.0.73.2) port 80 (#2)
    > GET /avatar/39522e007e90c6998be1f7514ac2ac84?s=96&r=G' srcset='https://secure.gravatar.com/avatar/39522e007e90c6998be1f7514ac2ac84?s=192 HTTP/1.1
    Host: www.gravatar.com
    Accept: */*
    
    < HTTP/1.1 400 Bad Request
    * Server nginx is not blacklisted
    < Server: nginx
    < Date: Mon, 28 Nov 2016 21:16:58 GMT
    < Transfer-Encoding: chunked
    < Connection: keep-alive
    <
    * Connection #2 to host www.gravatar.com left intact
    * Hostname was NOT found in DNS cache
    *   Trying 192.0.73.2...
    * Connected to www.gravatar.com (192.0.73.2) port 80 (#2)
    > GET /avatar/39522e007e90c6998be1f7514ac2ac84?s=120&r=G HTTP/1.1
    Host: www.gravatar.com
    Accept: */*
    
    < HTTP/1.1 302 Found
    * Server nginx is not blacklisted
    < Server: nginx
    < Date: Mon, 28 Nov 2016 21:16:10 GMT
    < Content-Type: text/html; charset=utf-8
    < Content-Length: 0
    < Connection: keep-alive
    < Last-Modified: Wed, 11 Jan 1984 08:00:00 GMT
    < Link: <{cut:valid-link}>; rel="canonical"
    < Location: {cut:valid-link}
    < X-nc: MISS ewr 3
    < Expires: Mon, 28 Nov 2016 21:21:10 GMT
    < Cache-Control: max-age=300
    < Source-Age: 0
    <
    * Connection #2 to host www.gravatar.com left intact
    * Hostname was found in DNS cache
    *   Trying 192.0.73.2...
    * Connected to www.gravatar.com (192.0.73.2) port 80 (#4)
    > GET /avatar/39522e007e90c6998be1f7514ac2ac84?s=96&r=G' srcset='https://secure.gravatar.com/avatar/39522e007e90c6998be1f7514ac2ac84?s=192 HTTP/1.1
    Host: www.gravatar.com
    Accept: */*
    
    < HTTP/1.1 400 Bad Request
    * Server nginx is not blacklisted
    < Server: nginx
    < Date: Mon, 28 Nov 2016 21:16:12 GMT
    < Transfer-Encoding: chunked
    < Connection: keep-alive
    <
    * Connection #4 to host www.gravatar.com left intact
    
Viewing 1 replies (of 1 total)
  • psuba

    (@psuba)

    I can see a very similar effect.
    I have an error in my error log file every time any page is viewed – it looks like the default (custom) avatar is being queried, the plugin tries to cache it but fails.
    The line in the logfile is below (I have redacted the bits that are irrelevant):

    PHP Warning: copy( http://redacted_url_path/filename.png
    ): failed to open stream: HTTP request failed! HTTP/1.1 400 Bad Request
    in /irrelevant_path/plugins/nix-gravatar-cache/nf-gravatar-cache.php on line 184

    The URL it is complaining about is actually valid and I can retrieve an image in a browser by copy/paste, so it looks like the problem is with how the copy function tries to retrieve a file.

    I actually had to manually place copies (with resize) of the avatar in the Gravatar cache folder location to avoid errors on my client side.

    It may be the same issue or something different but either way we are talking about a 400 error in the logfile caused by the plugin.

Viewing 1 replies (of 1 total)
  • The topic ‘nginx requests flooding error logs’ is closed to new replies.