ERR_CONTENT_DECODING_FAILED when try to access job configuration pages

2012-04-16 Thread Jason Axelson
Hi,

I'm getting Error 330 (net::ERR_CONTENT_DECODING_FAILED): Unknown
error. in Chrome when I try to access job configuration pages.
Firefox gives a more generic error but also cannot access it.

This is on Jenkins 1.459 running on Ubuntu 11.10. Nothing is showing
up in the Jenkins Log. This happens on all my projects even when I
create a new job (can't even set any of the settings but it still
creates the empty job). Does anyone have ideas what could cause this?

I am about to try restarting after some builds finish. And it works
after restarting but I still want to send this out in case anyone gets
a similar error.

It may be related to just installing 1.459 last Friday, not sure
exactly which version I was on before that but it was probably around
a month old.

Thanks,
Jason


Re: ERR_CONTENT_DECODING_FAILED when try to access job configuration pages

2012-04-16 Thread Didier Durand
Hi Jason,

I had this same problem with 1.458 on CentOS (due to the gzip page 
compression introduced then) 

see 
https://groups.google.com/forum/?fromgroups#!searchin/jenkinsci-users/cobertura/jenkinsci-users/OJxWOXpSsMs/ReNTRVSFkFAJ

I upgraded this morning to 1.460 and the problem disappeared: you may also 
try the update.

regards

didier

Le mardi 17 avril 2012 06:45:12 UTC+2, Jason Axelson a écrit :

 Hi,

 I'm getting Error 330 (net::ERR_CONTENT_DECODING_FAILED): Unknown
 error. in Chrome when I try to access job configuration pages.
 Firefox gives a more generic error but also cannot access it.

 This is on Jenkins 1.459 running on Ubuntu 11.10. Nothing is showing
 up in the Jenkins Log. This happens on all my projects even when I
 create a new job (can't even set any of the settings but it still
 creates the empty job). Does anyone have ideas what could cause this?

 I am about to try restarting after some builds finish. And it works
 after restarting but I still want to send this out in case anyone gets
 a similar error.

 It may be related to just installing 1.459 last Friday, not sure
 exactly which version I was on before that but it was probably around
 a month old.

 Thanks,
 Jason