[issue8450] httplib: false BadStatusLine() raised

[miss-islington]

miss-islington  added the comment:


New changeset ee78ba2c819b0cd7671a575e584d8fe1b7adb3e4 by Miss Islington (bot) 
(Shoham Peller) in branch '2.7':
[2.7] closes bpo-8450: a better error message when http status line isn't 
received (GH-2825)
https://github.com/python/cpython/commit/ee78ba2c819b0cd7671a575e584d8fe1b7adb3e4


--
nosy: +miss-islington
resolution:  -> fixed
stage: needs patch -> resolved
status: open -> closed

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue8450] httplib: false BadStatusLine() raised

[Shoham Peller]

Changes by Shoham Peller :


--
pull_requests: +2877

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue8450] httplib: false BadStatusLine() raised

[Roundup Robot]

Changes by Roundup Robot :


--
pull_requests: +1748

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue8450] httplib: false BadStatusLine() raised

[Roundup Robot]

Changes by Roundup Robot :


--
pull_requests: +1551

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue8450] httplib: false BadStatusLine() raised

[Martin Panter]

Martin Panter added the comment:

I don’t think so. It is best to avoid a new exception type (even a subclass) in 
a bug fix. That would break code which checks “type(exc) == BadStatusLine” or 
similar.

Specific exception messages are supposed to be implementation details, and the 
current message is already quirky due to the change from Issue 7427 (released 
in 2.7a4). That is why I thought it might be reasonable to just change the 
exception message in a bug fix.

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue8450] httplib: false BadStatusLine() raised

[Shoham Peller]

Shoham Peller added the comment:

How about back-porting the v3.5 fix, and the new "RemoteDisconnected" 
exception? Is that reasonable?

--
nosy: +Shoham Peller

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue8450] httplib: false BadStatusLine() raised

[Martin Panter]

Changes by Martin Panter :


--
stage:  -> needs patch
versions:  -Python 2.6, Python 3.1, Python 3.2

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue8450] httplib: false BadStatusLine() raised

[Martin Panter]

Changes by Martin Panter :


--
components: +Documentation

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue8450] httplib: false BadStatusLine() raised

[Martin Panter]

Martin Panter added the comment:

Issue 3566 has added a new exception subclass, RemoteDisconnected, in 3.5. 
People are still complaining about the old BadStatusLine exception in Python 2 
though. See Issue 23054.

Python 2 could still get better documentation of the BadStatusLine exception. 
Currently it gives the impression that it only happens when the “strict” 
parameter is True, and a status line was received that was not understood.

The exception message could also be improved. Due to Issue 7427, there is a 
special case to make the message literally two quote signs (''), representing 
an empty string. Perhaps messages like “End of stream signalled”, “No status 
line”, or “Empty status line” would be clearer.

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue8450] httplib: false BadStatusLine() raised

[Demian Brecht]

Demian Brecht added the comment:

This should likely be closed as a duplicate of #3566, which has additional 
detail.

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue8450] httplib: false BadStatusLine() raised

[Jakub Wilk]

Changes by Jakub Wilk :


--
nosy: +jwilk

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue8450] httplib: false BadStatusLine() raised

[Demian Brecht]

Changes by Demian Brecht :


--
nosy: +demian.brecht

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue8450] httplib: false BadStatusLine() raised

[Martin Panter]

Martin Panter added the comment:

Sorry the IncompleteRead reference was meant to be Issue 666219

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue8450] httplib: false BadStatusLine() raised

[Martin Panter]

Martin Panter added the comment:

See also Issue 3566, which also brings up the false BadStatusLine exception, 
and suggests some kind of retry logic.

Whatever exception it is, it could be documented better. In Issue 66621, the 
poster thought it should be an IncompleteRead exception.

--
nosy: +vadmium

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue8450] httplib: false BadStatusLine() raised

[karl]

karl added the comment:

Hmm no code.
I wonder if it's about this part.
http://hg.python.org/cpython/file/3.3/Lib/http/client.py#l321

--
nosy: +karlcow

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue8450] httplib: false BadStatusLine() raised

[Senthil Kumaran]

Changes by Senthil Kumaran :


--
assignee:  -> orsenthil

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue8450] httplib: false BadStatusLine() raised

[Dirkjan Ochtman]

Changes by Dirkjan Ochtman :


--
nosy: +djc

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue8450] httplib: false BadStatusLine() raised

[Antoine Pitrou]

Changes by Antoine Pitrou :


--
nosy: +orsenthil
priority:  -> normal
versions: +Python 2.7, Python 3.1, Python 3.2

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue8450] httplib: false BadStatusLine() raised

[mschu]

New submission from mschu :

Independent from HTTP strict, an invalid BadStatusLine() exception is raised 
when a keep-alive connection exceeds its timeout:

client->server 
s->c 

s->c: FIN/ACK
c->s: ACK
c->s: /FIN
s->c: RST (without data)

which raises the exception.

An easy workaround is to either poll information often enough for the server to 
not close the connection or close and reopen the connection. However, the 
exception is misleading.

--
components: Library (Lib)
messages: 103545
nosy: mschu
severity: normal
status: open
title: httplib: false BadStatusLine() raised
type: behavior
versions: Python 2.6

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com