Open bobbingwide opened 3 years ago
The GET-404
is returned when the request is for favicon.ico
.
The reason for returning a 404 was that in my opinion this file should be delivered by the web server.
It shouldn't need WordPress to return it.
When WordPress does return the favicon.ico is actually sets the HTTP response to 302
So we need to cater for this response code in the hardcoded filtering.
These don't report an HTTP response. Why not? Proabably because they're being invoked from the command line. I got a similar result running WP-CLI
\\d_drive\\dos\\wp-cli.phar,,6.341681,8.0.2,1271,3864,506,11,686,28,13,7,5,0.0023677349090576,,,,5824,127.0.0.1,6.340688,2021-03-14T13:21:45+00:00,,GET,
The Slog request type report run against
https://oik-plugins.uk/bwtrace/bwtrace.vt.20210313
reported 71GET-404
's but viewing the file I can only see one. What are the other 70?Additionally,
GET-404
isn't a request type I can filter on.As an aside. I also see requests from IP address 127.0.0.1 taking varying amounts of time.
These don't report an HTTP response. Why not?