Re: urllib2 and transfer-encoding = chunked

2007-01-20 Thread Nikita the Spider
In article <[EMAIL PROTECTED]>, [EMAIL PROTECTED] wrote: > Haha! My mistake. > > The error is that when a web server is chunking a web page only the > first chunk appears to be acquired by the urllib2.urlopen call. If you > check the headers, there is no 'Content-length' (as expected) and > in

Re: urllib2 and transfer-encoding = chunked

2007-01-18 Thread jdvolz
Haha! My mistake. The error is that when a web server is chunking a web page only the first chunk appears to be acquired by the urllib2.urlopen call. If you check the headers, there is no 'Content-length' (as expected) and instead there is 'transfer-encoding' = 'chunked'. I am getting about the

Re: urllib2 and transfer-encoding = chunked

2007-01-18 Thread Gabriel Genellina
<[EMAIL PROTECTED]> escribió en el mensaje news:[EMAIL PROTECTED] >I am having errors which appear to be linked to a previous bug in > urllib2 (and urllib) for v2.4 and v2.5 of Python. Has this been fixed? > Has anyone established a standard workaround? I keep finding old > posts about it, that

urllib2 and transfer-encoding = chunked

2007-01-18 Thread jdvolz
I am having errors which appear to be linked to a previous bug in urllib2 (and urllib) for v2.4 and v2.5 of Python. Has this been fixed? Has anyone established a standard workaround? I keep finding old posts about it, that basically give up and say "well it's a known bug." Any help would be gre