Cherokee Web Server

Scott Jarkoff | 1 Jun 2009 05:54

Wordpress and favicon's

I first want to say that Cherokee rocks. We recently migrated from
Apache to Cherokee and are not going to look back. It's really good
stuff!

With that said, I have run in to a slight problem. I've followed the
Wordpress cookbook from
http://www.cherokee-project.com/doc/cookbook_wordpress.html and have
Wordpress running without any problems. However, for some reason I am
unable to get the favicon.ico to show because it appears that request
is redirected to Wordpress rather than serving the actual favicon.

Any ideas what I could do to get this to display properly? I assume I
need to add a redirection handler of some sort.

Thanks in advance!

Regards,

--

-- 
Scott Jarkoff
http://techmiso.com/

headers

Alvaro Lopez Ortega | 1 Jun 2009 09:00

Re: Wordpress and favicon's

On 01-jun-09, at 05:54, Scott Jarkoff wrote:

> I first want to say that Cherokee rocks. We recently migrated from
> Apache to Cherokee and are not going to look back. It's really good
> stuff!

Thanks! (for the blog entry too..)

> With that said, I have run in to a slight problem. I've followed the
> Wordpress cookbook from
> http://www.cherokee-project.com/doc/cookbook_wordpress.html and have
> Wordpress running without any problems. However, for some reason I am
> unable to get the favicon.ico to show because it appears that request
> is redirected to Wordpress rather than serving the actual favicon.
>
> Any ideas what I could do to get this to display properly? I assume I
> need to add a redirection handler of some sort.

You'd have to add a new rule:

   Regular Expression: ^/favicon.ico$, Handler: Static Content,  
Final=checked.

It's very important that this rule is placed before the redirection,  
so when a request for /favicon.ico is received and the server  
evaluates the rule list (from top to bottom) it's matched before it's  
redirected to index.php.

Cheers!

(Continue reading)

headers

Oli Warner | 1 Jun 2009 09:31

Re: Wordpress and favicon's

I'll add: you need to restart your browser in-between changing favicon (even enabling it for the first time) because they're cached and can't be refreshed in the traditional control+f5/cache-clearing way.

On Mon, Jun 1, 2009 at 8:00 AM, Alvaro Lopez Ortega <alvaro <at> alobbs.com> wrote:

On 01-jun-09, at 05:54, Scott Jarkoff wrote:

> I first want to say that Cherokee rocks. We recently migrated from
> Apache to Cherokee and are not going to look back. It's really good
> stuff!

Thanks! (for the blog entry too..)

> With that said, I have run in to a slight problem. I've followed the
> Wordpress cookbook from
> http://www.cherokee-project.com/doc/cookbook_wordpress.html and have
> Wordpress running without any problems. However, for some reason I am
> unable to get the favicon.ico to show because it appears that request
> is redirected to Wordpress rather than serving the actual favicon.
>
> Any ideas what I could do to get this to display properly? I assume I
> need to add a redirection handler of some sort.

You'd have to add a new rule:

Regular Expression: ^/favicon.ico$, Handler: Static Content,
Final=checked.

It's very important that this rule is placed before the redirection,
so when a request for /favicon.ico is received and the server
evaluates the rule list (from top to bottom) it's matched before it's
redirected to index.php.

Cheers!

--
Octality
http://www.octality.com/

_______________________________________________
Cherokee mailing list
Cherokee <at> lists.octality.com
http://lists.octality.com/listinfo/cherokee

_______________________________________________
Cherokee mailing list
Cherokee <at> lists.octality.com
http://lists.octality.com/listinfo/cherokee

headers

Scott Jarkoff | 1 Jun 2009 13:06

Re: Wordpress and favicon's

On Mon, Jun 1, 2009 at 16:00, Alvaro Lopez Ortega <alvaro <at> alobbs.com> wrote:

> Thanks! (for the blog entry too..)

My pleasure. Gotta love good software like Cherokee. Not only does it
work better than advertised, but the community is awesome. I should
really be the one thanking you.

> You'd have to add a new rule:
>  Regular Expression: ^/favicon.ico$, Handler: Static Content, Final=checked.

Damn, I was so close! I had tried /favicon.ico$ and that did not work
so I tried a couple different variants. Had not thought to start with
the caret.

Many *many* _many_ thanks for the assistance. That totally worked. I'm
a favicon serving fool now.

Regards,

--

-- 
Scott Jarkoff
http://techmiso.com/

headers

Scott Jarkoff | 1 Jun 2009 13:08

Re: Wordpress and favicon's

On Mon, Jun 1, 2009 at 16:31, Oli Warner <oli <at> thepcspy.com> wrote:

> I'll add: you need to restart your browser in-between changing favicon (even
> enabling it for the first time) because they're cached and can't be
> refreshed in the traditional control+f5/cache-clearing way.

Right on. I was not actually waiting to see if the favicon would show
up. What I was doing to test was loading the favicon url in the
browser and continually was issued a 404 error. I was on the right
track but just missed that one single key.

Many thanks! Had it not been for you I would never have known about
Cherokee much less tried it.

Regards,

--

-- 
Scott Jarkoff
http://techmiso.com/

headers

Alejandro Barrera | 1 Jun 2009 17:34

debian/ubuntu package problem

Setting up libcherokee-config0 (0.99.15-1) ...
Usage: update-python-modules [-v] [-c] package_directory [...]
       update-python-modules [-v] [-c] package.dirs [...]
       update-python-modules [-v] [-a|-f|-p]

update-python-modules: error: /usr/share/python-support/libcherokee-
config0.private is not a directory
dpkg: error processing libcherokee-config0 (--configure):
 subprocess installed post-installation script returned error exit status 2
Errors were encountered while processing:
 libcherokee-config0
E: Sub-process /usr/bin/dpkg returned an error code (1)

Help anyone? 
--

-- 
http://www.neurosecurity.com

"We must be the change we wish to see in the world"
Mahatma Gandhi

headers

Gunnar Wolf | 1 Jun 2009 18:36

Re: debian/ubuntu package problem

Alejandro Barrera dijo [Mon, Jun 01, 2009 at 05:34:29PM +0200]:
> Setting up libcherokee-config0 (0.99.15-1) ...
> Usage: update-python-modules [-v] [-c] package_directory [...]
>        update-python-modules [-v] [-c] package.dirs [...]
>        update-python-modules [-v] [-a|-f|-p]
> 
> update-python-modules: error: /usr/share/python-support/libcherokee-
> config0.private is not a directory
> dpkg: error processing libcherokee-config0 (--configure):
>  subprocess installed post-installation script returned error exit status 2
> Errors were encountered while processing:
>  libcherokee-config0
> E: Sub-process /usr/bin/dpkg returned an error code (1)
> 
> Help anyone? 

Hi,

This was reported already:

http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=526835

I am stumped by this bug - But not only because of the bug's
appearance (everybody knows I can make mistakes big-time!), but
because it has so far affected _very_ few people (three, you
included). I feel it is more related to python-support than to us, as
I did no changes to anything Python-related.

Anyway - Please follow the bug
report. /usr/share/python-support/libcherokee-config0.private should
_not_ be a directory. And, if anything remains broken, please... tell
me :-/

Greetings,

--

-- 
Gunnar Wolf - gwolf <at> gwolf.org - (+52-55)5623-0154 / 1451-2244
PGP key 1024D/8BB527AF 2001-10-23
Fingerprint: 0C79 D2D1 2C4E 9CE4 5973  F800 D80E F35A 8BB5 27AF

headers

Alejandro Barrera | 1 Jun 2009 18:51

Re: debian/ubuntu package problem

> Hi,
>
> This was reported already:
>
> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=526835
>
> I am stumped by this bug - But not only because of the bug's
> appearance (everybody knows I can make mistakes big-time!), but
> because it has so far affected _very_ few people (three, you
> included). I feel it is more related to python-support than to us, as
> I did no changes to anything Python-related.
>
> Anyway - Please follow the bug
> report. /usr/share/python-support/libcherokee-config0.private should
> _not_ be a directory. And, if anything remains broken, please... tell
> me :-/

Fixed. The weird thing is that I hadn't python-support installed on that 
server, so I'm guessing debian created that package not long ago but forgot to 
make it depend on some others. Either way, shouldn't the upgrade had asked me 
to install the python-support package?

>
> Greetings,

Thanks a lot Gunner for the quick response.
Alex

--

-- 
http://www.neurosecurity.com

"We must be the change we wish to see in the world"
Mahatma Gandhi

headers

Koen Vermeer | 1 Jun 2009 19:04

Re: debian/ubuntu package problem

On Mon, 2009-06-01 at 11:36 -0500, Gunnar Wolf wrote:
> This was reported already:
> 
> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=526835
> 
> I am stumped by this bug - But not only because of the bug's
> appearance (everybody knows I can make mistakes big-time!), but
> because it has so far affected _very_ few people (three, you
> included). I feel it is more related to python-support than to us, as
> I did no changes to anything Python-related.

I don't think your statement on the number of people affected is really
true. I had the same problem, but found the bug report and fixed it by
upgrading python-support. Of course, I could have attached a 'me too' to
the bug report. But I don't think bugs in Debian are fixed based on
popular vote, so I generally keep quiet in cases like this.

BTW, it happened to me on at least two servers (on different
architectures).

Best,
Koen

headers

Gunnar Wolf | 1 Jun 2009 19:37

Re: debian/ubuntu package problem

Alejandro Barrera dijo [Mon, Jun 01, 2009 at 06:51:26PM +0200]:
> Fixed. The weird thing is that I hadn't python-support installed on that 
> server, so I'm guessing debian created that package not long ago but forgot to 
> make it depend on some others. Either way, shouldn't the upgrade had asked me 
> to install the python-support package?

Umh... That seems to be my problem then! Thanks for pointing it
out. Yes — I had included it as a Cherokee build dependency (i.e. it
is used when building the package), but not as a dependency at install
time. So, that explains why so few users were bitten by it: Mostly
everybody already has this package installed.

Ok, fixing the bug. Thanks a lot for pointing in the right direction! 

--

-- 
Gunnar Wolf - gwolf <at> gwolf.org - (+52-55)5623-0154 / 1451-2244
PGP key 1024D/8BB527AF 2001-10-23
Fingerprint: 0C79 D2D1 2C4E 9CE4 5973  F800 D80E F35A 8BB5 27AF
_______________________________________________
Cherokee mailing list
Cherokee <at> lists.octality.com
http://lists.octality.com/listinfo/cherokee

5	May 2013
35	April 2013
3	March 2013
55	February 2013
16	January 2013
60	December 2012
22	November 2012
31	October 2012
13	September 2012
7	August 2012
8	July 2012
22	June 2012
7	May 2012
28	April 2012
23	March 2012
63	February 2012
116	January 2012
82	December 2011
71	November 2011
83	October 2011
79	September 2011
66	August 2011
50	July 2011
83	June 2011
99	May 2011
106	April 2011
112	March 2011
174	February 2011
217	January 2011
209	December 2010
137	November 2010
230	October 2010
164	September 2010
120	August 2010
89	July 2010
255	June 2010
241	May 2010
175	April 2010
120	March 2010
163	February 2010
152	January 2010
215	December 2009
173	November 2009
258	October 2009
276	September 2009
299	August 2009
176	July 2009
224	June 2009
203	May 2009
199	April 2009
140	March 2009
92	February 2009
198	January 2009
143	December 2008
222	November 2008
254	October 2008
78	September 2008
152	August 2008
57	July 2008
71	June 2008
49	May 2008
63	April 2008
83	March 2008
43	February 2008
21	January 2008
47	December 2007
12	November 2007
51	October 2007
24	September 2007
25	August 2007
47	July 2007
46	June 2007
29	May 2007
38	April 2007
9	March 2007
46	February 2007
73	January 2007
88	December 2006
33	November 2006
86	October 2006
84	September 2006
88	August 2006
64	July 2006
29	June 2006
53	May 2006
64	April 2006
92	March 2006
72	February 2006
77	January 2006

Mon	Tue	Wed	Thu	Fri	Sat	Sun

1	2	3	4	5	6	7
8	9	10	11	12	13	14
15	16	17	18	19	20	21
22	23	24	25	26	27	28
29	30