huge number of "No header recd from client at" errors

[Spike]

Hi,

this has been discussed before in this github bug and Philip offered the following explanation:

P.s. The 'No header recd from client at 192.168.10.98 - errno: 0' messages are due to the javascript aborting on the browser. It is opening a number of connections and then closing them without making a request. This same thing was happening in previous versions, but they just gave a general connection exception message. This also happens on sites that work fine (I expect because their javascript is written to be more robust).

that's fair enough, however I'd like to at least check the calls made, however I can't see the url logged anywhere. Am I missing something? Is there a reason why the log line mentions the source ip, but not the url the client was trying to access?

thanks,

Spike

[Philip Pearce]

The 'No header recd from client at  ...'   log messages happens when the the client opens a connection and then closes the connection without making an http request, or fails to send a request before the connection is timed out.  So there is no way of telling what url the client may be trying to access as the client has not sent e2g this information.      Connections from browser engines should(will) never behave in this way, so the call must be from a javescript engine or from a non-browser app.

As no request has been made there is nothing to log in the access log.   The only information e2g has is the IP of where the request came from, which may be the client IP or a NATed IP.   If there is an excessive number of these from a single IP if may indicate that a device is trying to use proxy avoidance software or has an infection.

Regards

Philip

---

--
You received this message because you are subscribed to the Google Groups "e2guardian" group.
To unsubscribe from this group and stop receiving emails from it, send an email to e2guardian+...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.