You cannot.

"It's a necessary evil because even if you don't care about it the
browser will still request it, so it's better not to respond with a
404 Not Found." --
http://developer.yahoo.com/performance/rules.html#favicon

-- Yoan

On Tue, May 6, 2008 at 4:38 AM, flywood <[EMAIL PROTECTED]> wrote:
>
>  I met same problem here. how can I disable this action which getting
>  the favicon.ico file?
>
>
>  On 5月3日, 上午11时57分, Justin Davis <[EMAIL PROTECTED]> wrote:
>  > The browser assumes that your favicon file will be located at /
>  > facicon.ico, but you haven't provided one there.  A good way to fix
>  > this is to put this in the <head> part of your html:
>  >
>  > <link rel="shorcut icon" href="/static/favicon.ico"/>
>  >
>  > And then create an icon file in your static folder, called
>  > favicon.ico.  It's a funny image format -- check 
> outhttp://www.nongnu.org/icoutils/
>
>
> > to learn more about how to make them.
>  >
>  > Cheers,
>  > Justin
>  >
>  > On May 2, 10:32 pm, dineshv <[EMAIL PROTECTED]> wrote:
>  >
>  > > I'm still in development and using the web.py local host and suddenly
>  > > in the past few days I get /favicon.ico 404 errors.  Here is some
>  > > output:
>  >
>  > > C:\... \py>python ac.py 127.0.0.1:8080http://127.0.0.1:8080/
>  > > localhost - - [02/May/2008 19:18:17] "GET / HTTP/1.1" 200 -
>  > > localhost - - [02/May/2008 19:18:59] "GET /static/graphics/logo_ac-
>  > > top.gif HTTP/1.1" 200 -
>  > > localhost - - [02/May/2008 19:18:59] "GET /favicon.ico HTTP/1.1" 404 -
>  > > localhost - - [02/May/2008 19:18:59] "GET /favicon.ico HTTP/1.1" 404 -
>  >
>  > > Any ideas what I can do?
>  >
>

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"web.py" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/webpy?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to