One of the BBC/CCE participants has run into problems with 'Unrecognized HTTP content - encoding' errors, can anybody help out?

http://bbc.cpdn.org/forum_thread.php?id=4604

12/08/2006 22:56:02|BBC Climate Change Experiment|Sending scheduler request to http://bbc.cpdn.org/bbc_cgi/cgi
12/08/2006 22:56:02|BBC Climate Change Experiment|Reason: Requested by user
12/08/2006 22:56:02|BBC Climate Change Experiment|(not requesting new work or reporting completed tasks)
12/08/2006 22:56:28||Project communication failed: attempting access to reference site
12/08/2006 22:56:30||Access to reference site succeeded - project servers may be temporarily down.
12/08/2006 22:56:32|BBC Climate Change Experiment|Scheduler request failed: Unrecognized HTTP Content-Encoding
12/08/2006 22:56:32|BBC Climate Change Experiment|Deferring scheduler requests for 5 minutes and 15 seconds

Just to update on whats going on.....

Today i have had different error messages appearing throughout the day, as shown below.

15/08/2006 11:52:46|BBC Climate Change Experiment|Scheduler request failed: Error 466
15/08/2006 13:18:05|BBC Climate Change Experiment|Scheduler request failed: Unrecognized HTTP Content-Encoding
15/08/2006 13:23:36|BBC Climate Change Experiment|Scheduler request failed: Error 466
15/08/2006 13:35:27|BBC Climate Change Experiment|Scheduler request failed: Unrecognized HTTP Content-Encoding
15/08/2006 20:12:10|BBC Climate Change Experiment|Scheduler request failed: HTTP internal server error
15/08/2006 20:18:42|BBC Climate Change Experiment|Scheduler request failed: a timeout was reached
15/08/2006 20:22:02|BBC Climate Change Experiment|Scheduler request failed: HTTP internal server error
15/08/2006 20:28:22|BBC Climate Change Experiment|Scheduler request failed: a timeout was reached
15/08/2006 20:31:43|BBC Climate Change Experiment|Scheduler request failed: HTTP internal server error

---

If you can, have him or her pass by on this post and post the specific information in that thread or to my email.

---

Better yet, let him or her answer in this thread. I set one up specially for this.

---

I've added a link to the new thread, it sounds like an 'interesting' problem! (Developer speak for a real puzzle...)

---

A zlib problem coming from cURL?

It would be interesting to see the phpinfo() output, especially HTTP_ACCEPT_ENCODING, when a web page with that command is downloaded with BOINC. If HTTP_ACCEPT_ENCODING promises more than BOINC can handle, the web server might send data that BOINC cannot decode, if the web page header starts with ob_start("ob_gzhandler");

I checked it for 5.2.13, BOINC does not set HTTP_ACCEPT_ENCODING in that version.

Testing it is easy, just try to attach BOINC to a phpinfo() web page, it will not accept that as a project but it will still download it with the name get_project_config.xml

In my test it didn't matter that it tried to download ...../phpinfo.php/get_project_config.php, the last part got ignored.