[wp-trac] Re: [WordPress Trac] #3426: Should include default favicon

WordPress Trac wp-trac at lists.automattic.com
Thu Jun 18 20:19:23 GMT 2009


#3426: Should include default favicon
---------------------------------+------------------------------------------
 Reporter:  robertaccettura      |        Owner:  cpoteet 
     Type:  defect (bug)         |       Status:  reopened
 Priority:  normal               |    Milestone:  2.9     
Component:  Performance          |      Version:  2.8     
 Severity:  normal               |   Resolution:          
 Keywords:  favicon needs-patch  |  
---------------------------------+------------------------------------------
Changes (by westi):

  * keywords:  favicon => favicon needs-patch


Comment:

 Replying to [comment:13 lloydbudd]:
 > Replying to [comment:11 mrmist]:
 > >
 > > Absolutely -1 to just dropping the .ico file in regardless,
 potentially undoing people's work.
 >
 > I'm calling this a defect and think this should be revisited. Although,
 it is not common for a heavily trafficked site not to have a favicon it
 seems to be a significant problem for web hosts:
 >
 > http://blog.nearlyfreespeech.net/2009/06/16/quick-wordpress-performance-
 tip-create-a-favicon/
 >
 > http://www.dreamhoststatus.com/2009/06/10/faviconico-favicongif-and-
 robotstxt-update/
 >
 >
 > Possible Solution:
 >
 > If the request gets to WordPress then a favicon does not exist, so
 WordPress can serve up WordPress's logo favicon from wp-includes/images/
 >
 > Generally I want to stay away from adding / modifying the favicon
 information in the <header>
 >
 > To Investigate:
 >
 > Any solution would want to confirm that it works with popular caching
 solutions such as supercache and batcache.

 I think if the request gets to WordPress then the shared hosts have
 already lost anyway.

 While we can improve on the performance of serving a 404 page by sending
 out the icon if it gets to WordPress.  I am not sure that is going to make
 it as good for the shared hosts as the files being there.

 Maybe we could add rewrite rules to the htaccess for these specific files
 instead?

-- 
Ticket URL: <http://core.trac.wordpress.org/ticket/3426#comment:15>
WordPress Trac <http://core.trac.wordpress.org/>
WordPress blogging software


More information about the wp-trac mailing list