requests for a
file favicon.ico that should have been, or so the client connecting
believes, in the root of my htdocs. The conections come from different
hosts, and at least in some it seems to be running Konqueror, so it is
not a Windows worm: GET / HTTP/1.1 200 1004 - Mozilla/5.0
(compatible
of hits on how to create such an icon
if you want to have one of your own.
Otherwise, just ignore these requests. :-)
HTH, Harry
- --On Wednesday, October 06, 2004 11:37:24 +0300 Emil Perhinschi
[EMAIL PROTECTED] wrote:
Sorry to bother, but is this an attack? I get repeated requests
Am 2004-10-06 11:37:24, schrieb Emil Perhinschi:
Sorry to bother, but is this an attack? I get repeated requests for a
file favicon.ico that should have been, or so the client connecting
believes, in the root of my htdocs. The conections come from different
hosts, and at least in some
On Wed, Oct 06, 2004 at 11:37:24AM +0300, Emil Perhinschi wrote:
Sorry to bother, but is this an attack? I get repeated requests for a
file favicon.ico that should have been, or so the client connecting
believes, in the root of my htdocs. The conections come from different
hosts
Perhinschi
Cc: [EMAIL PROTECTED]
Subject: Re: repeated requests for a file favicon.ico
On Wed, Oct 06, 2004 at 11:37:24AM +0300, Emil Perhinschi wrote:
Sorry to bother, but is this an attack? I get repeated requests for a
file favicon.ico that should have been, or so the client connecting
On 6 Oct 2004, Emil Perhinschi wrote:
Sorry to bother, but is this an attack? I get repeated requests for a
file favicon.ico that should have been, or so the client connecting
believes, in the root of my htdocs.
Yup. Ages ago Microsoft added support for displaying that icon next to
various
On Wed, Oct 06, 2004 at 11:43:21AM +0200, Jasper Filon wrote:
I have a little issue with the favicon file. My www root is password
protected. But i also have a /public directory, which can be accessed by
everyone. However, when someone opens a picture in his webbrowser by
opening
On Wed, Oct 06, 2004 at 12:22:47PM +0200, Jasper Filon wrote:
I agree with you that maybe it would be better if the browser would
interpret a authorisation request on a favicon.ico as a 404 (or 403)
error, but on the other hand, the request for favicon isn't any different
from a normal http
-required
message on favicon should be interpreted as a 404.
Regards, Jasper
-Original Message-
From: Matthew Palmer [mailto:[EMAIL PROTECTED]
Sent: woensdag 6 oktober 2004 14:10
To: [EMAIL PROTECTED]
Subject: Re: repeated requests for a file favicon.ico
On Wed, Oct 06, 2004 at 12:22:47PM
9 matches
Mail list logo
