unknown error

cpm18 · Post by **cpm18** » Mon Jun 21, 2010 12:18 pm

What does the following error mean?

58: Cannot decode deflate data via zlib: incorrect header check in the function TXzlibTranslate
is invalid

The page I had fetched seems to have problems when <urlcp httpversion 1.1> is set. When it is set to 1.0 there is no problems.

I am just curious about this because generally I have found some pages which are problematic when fetched with 1.0 set. Setting to 1.1 usually solved those problems. Perhaps it was just a fluke, but I haden't yet seen any cases where 1.0 worked better then 1.1.

Post by **Kai** » Mon Jun 21, 2010 4:49 pm

The error could indicate problems with the source data, or a problem with how <fetch> is dealing with it. Is it a public URL that you can list (mark private if needed, or open a tech support ticket). We'd need to reproduce it to diagnose further.

cpm18 · Post by **cpm18** » Wed Jun 23, 2010 10:00 am

I can't produce the exact error I listed above. But I do get an Encoding error for the following page when using 1.1 but not with 1.0.

http://boards.babycenter.ca/bcCAbclub20 ... tid=246740

Post by **Kai** » Wed Jun 23, 2010 5:58 pm

Yes, I get your message #1 error on that URL. Contact support at Thunderstone (link above); this appears to be an issue with the deflate decoder in <fetch>.

Post by **Kai** » Thu Jun 24, 2010 6:03 pm

Turns out it is actually an issue with the web server not being 100% in line with the HTTP/1.1 spec for the deflate encoding. But it also appears to be a common "violation" on the web, so we're adapting <fetch> to it.

In the meantime, a workaround is to disable the deflate decoder in <fetch>, so that the web server will have to choose another encoding:

<urlcp encodings del deflate>