You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
urllib2. strange behavior for getting chuncked transfer-ecnoded data #46496
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 nevertheless. It seems to me that this key in header need to be removed from the header if httplib "unchuncked" the data.
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.
Activity
begemoth commentedon Mar 6, 2008
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 nevertheless. It seems to me that this key in header need to be removed from the header if httplib "unchuncked" the data.
birkenfeld commentedon Mar 21, 2008
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.