[issue2243] urllib2. strange behavior for getting chuncked transfer-ecnoded data

Changes by Georg Brandl <[EMAIL PROTECTED]>: -- status: pending -> closed __ Tracker <[EMAIL PROTECTED]> __ ___ Python-bugs-list mailing list Un

[issue2243] urllib2. strange behavior for getting chuncked transfer-ecnoded data

Georg Brandl <[EMAIL PROTECTED]> added the comment: I don't think we should change this -- it sounds like gratuitous breakage to me, and I also don't see the reason why httplib should throw away an HTTP header just because the user isn't likely to need it. -- resolution: -> wont fix sta

[issue2243] urllib2. strange behavior for getting chuncked transfer-ecnoded data

Changes by Sean Reifschneider <[EMAIL PROTECTED]>: -- assignee: -> georg.brandl nosy: +georg.brandl priority: -> normal __ Tracker <[EMAIL PROTECTED]> __

[issue2243] urllib2. strange behavior for getting chuncked transfer-ecnoded data

New submission from begemoth: Through urllib2 open web pages from some sites (www.rbc.ru, www.rambler.ru, www.yandex.ru). Their servers send data in chuncked transfer-encoding. httplib (which is used by urllib2) "unchunk" data but I recieve "transfer-encoding: chuncked" in response header neve