Hi,
Is there any documentation on how django behaves during a GET /favicon.ico?
In my django 1.4.5 installation with runserver, GET /favicon.ico redirects
to /media/img/favicon; on OpenShift, it redirects to /media/favicon.ico.
My googlefu has failed me.
--
You received this message because yo
i was working with php and always i put the favicon.ico in the root of
the website but now the problem with django occurs
now i'm working with django and i have a problem now
i used
1. static.serve
2. .htaccess
3.redirect_to
but none of them works have you any idea for using favicon.ico in the
we
On 5/08/2013 4:22am, Tundebabzy wrote:
Hi,
Is there any documentation on how django behaves during a GET
/favicon.ico? In my django 1.4.5 installation with runserver, GET
/favicon.ico redirects to /media/img/favicon; on OpenShift, it redirects
to /media/favicon.ico.
It is a static image no diff
On Sun, Aug 4, 2013 at 11:56 PM, Mike Dewhirst wrote:
> On 5/08/2013 4:22am, Tundebabzy wrote:
>
>> Hi,
>> Is there any documentation on how django behaves during a GET
>> /favicon.ico? In my django 1.4.5 installation with runserver, GET
>> /favicon.ico redirects to /media/img/favicon; on OpenShif
On Dec 16, 9:45 pm, architecture wrote:
> i was working with php and always i put the favicon.ico in the root of
> the website but now the problem with django occurs
> now i'm working with django and i have a problem now
> i used
> 1. static.serve
> 2. .htaccess
> 3.redirect_to
>
> but none of th
On Tue, 2008-12-16 at 02:45 -0800, architecture wrote:
> i was working with php and always i put the favicon.ico in the root of
> the website but now the problem with django occurs
> now i'm working with django and i have a problem now
> i used
> 1. static.serve
> 2. .htaccess
> 3.redirect_to
>
HI,
> I haven't bothered to try fixing it yet, but I wonder if a redirect
> from /favicon.ico to /media/images/favicon.ico might solve that issue.
> If I get a chance I'll test it today, see if works. Has anyone else
> experimented with this?
Well, at least a couple of ways to fix that. If you
I've done favicons as per Malcolm's suggestion, with a link in my base
template to e.g. /media/images/favicon.ico, and that works
satisfactorily for most cases. The favicon shows as expected in
browser address bars, etc.
However, since favicons arose via convention, where the convention was
to p
you can put it directly in your http-vhosts.conf file
ServerName crucial-systems.com
DocumentRoot /home/crucial/crucial-stack/crucialwww
... etc...
Alias /favicon.ico "/home/crucial/crucial-stack/crucialwww/favicon.ico"
...
WSGIScriptAlias / /home/crucial/crucial-stac
On Dec 18, 10:12 am, felix wrote:
> you can put it directly in your http-vhosts.conf file
>
>
> ServerName crucial-systems.com
> DocumentRoot /home/crucial/crucial-stack/crucialwww
> ... etc...
>
> Alias /favicon.ico "/home/crucial/crucial-stack/crucialwww/favicon.ico
10 matches
Mail list logo