That's only for IE4 really... with modern browsers you can specify where the
favourite icon is via mark up:

http://en.wikipedia.org/wiki/Favicon

Change your layouts and your done.

On Fri, Sep 4, 2009 at 10:21 AM, Jan Limpens <[email protected]> wrote:

> but i would have to add a favicon to every fake directory (which is mapped
> to a controller), and probably then the controllers would stopp responding
> as well
>
> so, www.site.com/favicon.ico is no problem, but I get loads of requests
> for www.site.com/somecontroller/favicon.ico - these I have to handle
> somehow in code.
>
> 2009/9/3 John Simons <[email protected]>
>
>
>> I should add a bit more!
>>
>> The routing in Monorail first checks if the requested file physically
>> exists and if it does than it skips the routing otherwise performs the
>> routing.
>>
>>
>> On Sep 4, 7:51 am, John Simons <[email protected]> wrote:
>> > Add a favicon ;)
>> > And you don't need to add anything to the routing
>> >
>> > On Sep 3, 10:17 pm, Jan Limpens <[email protected]> wrote:
>> >
>> > > Thought so as well, but am a bit unsure of the actual
>> implementation...
>> > > "<controller>/favicon.ico" still would route it through some
>> controller.
>> > > A "StaticController" then could send it via 301 to the static file in
>> the
>> > > root...
>> >
>> > > 2009/9/3 Ayende Rahien <[email protected]>
>> >
>> > > > routing?
>> >
>> > > > On Thu, Sep 3, 2009 at 2:40 PM, Jan Limpens <[email protected]>
>> wrote:
>> >
>> > > >> What would be the smartest way to get rid of these 404s I get on
>> > > >> controllername/favicon?
>> >
>> > > >> --
>> > > >> Jan
>> >
>> > > --
>> > > Jan
>>
>>
>
>
> --
> Jan
>
> >
>

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"Castle Project Users" 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/castle-project-users?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to