Prev: how to let shell.SendKeys use unicode on windows in python
Next: File Manager in Tkinter
From: Navkirat Singh on 10 Aug 2010 00:32
Hi guys,

I am having this strange problem. I have programmed a very basic multiprocessing webserver using low level sockets. Each time the server receives a request it spawns a new process to handle the request. Now when through a web browser I type http://localhost:8001/ it automatically creates two processes: One process to server the '/' path and another one to serve the '/favicon.ico' path. I have not programmed it to serve the latter. Infact I dont even know where that name '/favicon.ico' comes from. Any insight into this weird behavior would be greatly appreciated.

Regards,
Nav
From: Ned Deily on 10 Aug 2010 00:48
In article <9F21F146-A43A-4108-962B-4DFA14E430E4(a)gmail.com>,
Navkirat Singh <navkirats(a)gmail.com> wrote:
> I am having this strange problem. I have programmed a very basic
> multiprocessing webserver using low level sockets. Each time the server
> receives a request it spawns a new process to handle the request. Now when
> through a web browser I type http://localhost:8001/ it automatically creates
> two processes: One process to server the '/' path and another one to serve
> the '/favicon.ico' path. I have not programmed it to serve the latter. Infact
> I dont even know where that name '/favicon.ico' comes from. Any insight into
> this weird behavior would be greatly appreciated.

It's not the server's doing, it's the web browser requesting the
favicon. See http://en.wikipedia.org/wiki/Favicon

--
Ned Deily,
nad(a)acm.org

From: Chris Gonnerman on 10 Aug 2010 00:56
On 08/09/2010 11:32 PM, Navkirat Singh wrote:
> I am having this strange problem. I have programmed a very basic multiprocessing webserver using low level sockets. Each time the server receives a request it spawns a new process to handle the request. Now when through a web browser I type http://localhost:8001/ it automatically creates two processes: One process to server the '/' path and another one to serve the '/favicon.ico' path. I have not programmed it to serve the latter. Infact I dont even know where that name '/favicon.ico' comes from. Any insight into this weird behavior would be greatly appreciated.
>
All modern browsers attempt to retrieve this file from any web server
visited; it becomes the website's icon in any shortcut/deskcut, and
appears on the address bar beside the URL.

Short answer: You can safely ignore it.

-- Chris.

From: Gabriel Genellina on 12 Aug 2010 01:20
En Tue, 10 Aug 2010 01:32:49 -0300, Navkirat Singh <navkirats(a)gmail.com>
escribi�:

> I am having this strange problem. I have programmed a very basic
> multiprocessing webserver using low level sockets. Each time the server
> receives a request it spawns a new process to handle the request. Now
> when through a web browser I type http://localhost:8001/ it
> automatically creates two processes: One process to server the '/' path
> and another one to serve the '/favicon.ico' path. I have not programmed
> it to serve the latter. Infact I dont even know where that name
> '/favicon.ico' comes from. Any insight into this weird behavior would be
> greatly appreciated.

It't the browser attempting to get an icon for the page.
See http://en.wikipedia.org/wiki/Favicon

--
Gabriel Genellina

 | 
Pages: 1
Prev: how to let shell.SendKeys use unicode on windows in python
Next: File Manager in Tkinter