On Fri, Oct 14, 2011 at 9:56 PM, Steve Swift swi...@swiftys.org.uk wrote:
It is surprising that the installation of apache does not install a sample
favicon.ico (the apache feather, perhaps).
Apache used to* install a more complete welcome page, with favicon,
links to docs, everything a
Is not relevant; You're going to get the accesses in there whether they
result in 200 or 404.
On 15 October 2011 06:35, Dan Trainor dan.trai...@gmail.com wrote:
And the access log?
On Oct 14, 2011 9:59 PM, Steve Swift swi...@swiftys.org.uk wrote:
I don't have any particular axe to grind, but
Wild Bill Miller
Swampmaster
--
From: Wild Bill Miller wildbillsemail...@comcast.net
Sent: Friday, October 14, 2011 1:30 AM
To: users-i...@httpd.apache.org
Subject: favicon.ico
I am new to the Apache web server.
When I inquire on my domain
On one hand: favicon.ico must be readable by the process which runs
the web server. Check the ACL on that file.
On the other hand: it is not an error if favicon.ico does not exist.
That's the small image which is typically displayed just to the left
of the URL entry field near the top of the
It is surprising that the installation of apache does not install a sample
favicon.ico (the apache feather, perhaps).
On 14 October 2011 14:34, Mark H. Wood mw...@iupui.edu wrote:
On one hand: favicon.ico must be readable by the process which runs
the web server. Check the ACL on that file.
On 10/14/2011 3:56 PM, Steve Swift wrote:
It is surprising that the installation of apache does not install a sample
favicon.ico
(the apache feather, perhaps).
Wouldn't happen. Take a look at the modern rendition of 'it worked'.
htmlbodyh1It works!/h1/body/html
The arbitrary user installs
At 09:56 PM 10/14/2011 +0100, Steve Swift wrote:
It is surprising that the installation of apache does not install a sample
favicon.ico (the apache feather, perhaps).
Why? It's already above and beyond that httpd gives you a success
page. A server is designed to serve what *you* want -- and
I don't have any particular axe to grind, but putting a favicon.ico in the
documentroot would avoid the error log starting to fill from the outset.
Also, for someone who had just installed their first ever server, it would
give them a clue how to get their own icon to appear in the browser. This
And the access log?
On Oct 14, 2011 9:59 PM, Steve Swift swi...@swiftys.org.uk wrote:
I don't have any particular axe to grind, but putting a favicon.ico in the
documentroot would avoid the error log starting to fill from the outset.
Also, for someone who had just installed their first ever
