summaryrefslogtreecommitdiff
path: root/Lib/httplib.py
Commit message (Collapse)AuthorAgeFilesLines
* Strip square brackets from IPv6 address.Martin v. Löwis2004-09-141-0/+2
|
* missed the obvious test case and corresponding fixSkip Montanaro2004-09-141-1/+2
|
* Search from the end of the host/port combination to find the colon whichSkip Montanaro2004-09-141-1/+1
| | | | separates ip address from the port to accommodate ipv6 addresses.
* Patch #800236: add HTTPResponse.getheaders().Martin v. Löwis2004-08-181-0/+6
|
* SF bug 874842 and patch 997626: httplib bugsJeremy Hylton2004-08-071-10/+20
| | | | | | Hack httplib to work with broken Akamai proxies. Make sure that httplib doesn't add extract Accept-Encoding or Content-Length headers if the client has already set them.
* Fix a bug that robotparser starves memory when the server responsesHye-Shik Chang2004-06-051-1/+9
| | | | | in HTTP/0.9 due to dissonance of httplib.LineAndFileWrapper and urllib.addbase.
* Replace str.find()!=1 with the more readable "in" operator.Raymond Hettinger2004-05-041-2/+2
|
* Whitespace normalization.Tim Peters2004-01-181-2/+2
|
* Patch #831747: Add skip_accept_encoding parameter to putrequest.Martin v. Löwis2003-11-191-3/+7
|
* fixed obvious bug in _send_header as per SF bug #831271Alex Martelli2003-11-091-2/+1
| | | | (same as commit of Sun Nov 2 to the release23-maint branch)
* Patch #817854: Add missing operations for SSLFile. Fixes #792101.Martin v. Löwis2003-10-271-0/+25
| | | | Backported to 2.3.
* Fix sf bug 666219: assertion error in httplib.Jeremy Hylton2003-06-291-0/+4
| | | | The obvious way for this assertion to fail is if the LineAndFileWrapper constructor is called when an empty line. Raise a BadStatusError before the call.
* Deal with a couple XXX comments which asked questions.Greg Stein2003-06-241-4/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | In response to "shouldn't the client close the file?", the answer is "no". The original design behind HTTPConnection is that the client did not have to worry about it. The response would close itself when you read the last of the data from it. This closing also dealt with allowing the connection to perform another request/response (if it was a persistent connection). However... the auto-close behavior broke compatibility with the classic httplib.HTTP class' behavior when a zero-length response body was present. In that situation, the HTTPResponse object was auto-closing it since there was no data present, and for an HTTP/1.0 connection-close socket (or an HTTP/0.9 request) connection, that also ended up closing the socket. When an httplib.HTTP user went to read the socket... boom. A patch to correct the auto-close (for compat with old httplib users) was added in rev 1.22. But for non-zero-length *chunked* bodies, we should keep the auto-close behavior. The library user is not reading the socket (they can't cuz of the chunked response we just got done handling), so they should be immune to the response closing the socket. In fact, I would like to see (one day) the auto-close restored, and the HTTP subclass would simply have a flag to disable that behavior (for back-compat purposes).
* Always unwrap _socketobj in socket.ssl. Revert httplib.py 1.25.Martin v. Löwis2003-06-141-4/+1
| | | | Fixes #754447.
* Whitespace normalization.Tim Peters2003-05-121-1/+1
|
* SF bug 622042: Don't expect response body from HEAD request.Jeremy Hylton2003-05-051-4/+11
| | | | Bug fix candidate.
* Implement IDNA (Internationalized Domain Names in Applications).Martin v. Löwis2003-04-181-3/+3
|
* Reverted the previous change to read() and readline().Raymond Hettinger2003-03-061-18/+28
| | | | | | Kevin Jacobs found that the code simplification did not exactly match the semantics of the original. Regression test cases were requested.
* Module review:Raymond Hettinger2003-02-261-40/+30
| | | | | | | * Replaced "while 1" with "while True" * Rewrote read() and readline() for clarity and speed. * Replaced variable 'list' with 'hlist' * Used augmented assignment in two places.
* typoSkip Montanaro2003-02-251-1/+1
|
* Whitespace normalization.Tim Peters2002-11-241-1/+1
|
* Remove some test code.Jeremy Hylton2002-11-131-33/+0
| | | | | The buggy yahoo server was fixed, and the opalgroup test files are gone.
* Fix SF bug #637789: Handle Proxy-Connection header.Jeremy Hylton2002-11-131-15/+25
| | | | Also, remove unused local variable noted by pychecker.
* Whitespace normalization.Tim Peters2002-11-091-2/+2
|
* Move code for reading chunked responses in helper function,Jeremy Hylton2002-09-031-45/+52
| | | | along with some small changes (e.g. use of +=).
* SF bug [ 600488 ] Robustness tweak to httplib.pyJeremy Hylton2002-09-031-3/+1
| | | | | If the transfer-encoding is unknown, ignore it. Suggested by Tom Emerson.
* Whitespace normalization.Tim Peters2002-08-081-1/+1
|
* typoSkip Montanaro2002-07-251-1/+1
|
* Fix typos and such caught by the pycheckerbot.Jeremy Hylton2002-07-161-3/+3
|
* Whitespace normalization.Tim Peters2002-07-161-6/+6
|
* Send HTTP requests with a single send() call instead of many.Jeremy Hylton2002-07-161-15/+26
| | | | | | | | | | | | | | | | | | | | | | The implementation now stores all the lines of the request in a buffer and makes a single send() call when the request is finished, specifically when endheaders() is called. This appears to improve performance. The old code called send() for each line. The sends are all short, so they caused bad interactions with the Nagle algorithm and delayed acknowledgements. In simple tests, the second packet was delayed by 100s of ms. The second send was delayed by the Nagle algorithm, waiting for the ack. The delayed ack strategy delays the ack in hopes of piggybacking it on a data packet, but the server won't send any data until it receives the complete request. This change minimizes the problem that Nagle + delayed ack will cause a problem, although a request large enough to be broken into two packets will still suffer some delay. Luckily the MSS is large enough to accomodate most single packets. XXX Bug fix candidate?
* Change _begin() back to begin().Jeremy Hylton2002-07-121-3/+2
| | | | Client code could create responses explicitly.
* Fix for SF bug 579107.Jeremy Hylton2002-07-091-36/+88
| | | | | | | | | | The recent SSL changes resulted in important, but subtle changes to close() semantics. Since builtin socket makefile() is not called for SSL connections, we don't get separately closeable fds for connection and response. Comments in the code explain how to restore makefile semantics. Bug fix candidate.
* Fix for SF bug #432621: httplib: multiple Set-Cookie headersJeremy Hylton2002-07-071-2/+108
| | | | | | | | | | If multiple header fields with the same name occur, they are combined according to the rules in RFC 2616 sec 4.2: Appending each subsequent field-value to the first, each separated by a comma. The order in which header fields with the same field-name are received is significant to the interpretation of the combined field value.
* Fix SF bug #575360Jeremy Hylton2002-07-061-0/+6
| | | | | | | Subclasses of Exception that define an __init__ must call Exception.__init__ or define self.args. Otherwise, str() will fail. Bug fix candidate.
* Handle HTTP/0.9 responses.Jeremy Hylton2002-07-061-19/+132
| | | | | | | | | | | | | | | | | | | | | | | | | | | | Section 19.6 of RFC 2616 (HTTP/1.1): It is beyond the scope of a protocol specification to mandate compliance with previous versions. HTTP/1.1 was deliberately designed, however, to make supporting previous versions easy.... And we would expect HTTP/1.1 clients to: - recognize the format of the Status-Line for HTTP/1.0 and 1.1 responses; - understand any valid response in the format of HTTP/0.9, 1.0, or 1.1. The changes to the code do handle response in the format of HTTP/0.9. Some users may consider this a bug because all responses with a sufficiently corrupted status line will look like an HTTP/0.9 response. These users can pass strict=1 to the HTTP constructors to get a BadStatusLine exception instead. While this is a new feature of sorts, it enhances the robustness of the code (be tolerant in what you accept). Thus, I consider it a bug fix candidate. XXX strict needs to be documented.
* Convert raise to call exception class. Add whitespace.Jeremy Hylton2002-07-021-1/+1
|
* Simplify HTTPSConnection constructor.Jeremy Hylton2002-06-281-21/+7
| | | | See discussion in SF bug 458463.
* Fixes for two separate HTTP/1.1 bugs: 100 responses and HTTPS connections.Jeremy Hylton2002-06-281-32/+102
| | | | | | | | | | | | | | | | | | | | | | | The HTTPResponse class now handles 100 continue responses, instead of choking on them. It detects them internally in the _begin() method and ignores them. Based on a patch by Bob Kline. This closes SF bugs 498149 and 551273. The FakeSocket class (for SSL) is now usable with HTTP/1.1 connections. The old version of the code could not work with persistent connections, because the makefile() implementation read until EOF before returning. If the connection is persistent, the server sends a response and leaves the connection open. A client that reads until EOF will block until the server gives up on the connection -- more than a minute in my test case. The problem was fixed by implementing a reasonable makefile(). It reads data only when it is needed by the layers above it. It's implementation uses an internal buffer with a default size of 8192. Also, rename begin() method of HTTPResponse to _begin() because it should only be called by the HTTPConnection.
* SF 563203. Replaced 'has_key()' with 'in'.Raymond Hettinger2002-06-011-1/+1
|
* Forward port of patch # 500311: Work around for buggy https servers.Martin v. Löwis2002-04-201-1/+2
| | | | Fixes #494762.
* oops - export InvalidURL in __all__Skip Montanaro2002-03-241-1/+1
|
* add InvalidURL exception - raised if port is given but empty or non-numericSkip Montanaro2002-03-241-1/+7
|
* [Bug #531616] Make HTTPS work again by adding a sendall method to theAndrew M. Kuchling2002-03-181-0/+3
| | | | | | | | | | FakeSocket class. Without it, the sendall() call got the method on the underlying socket object, and that messed up SSL. Does httplib use other methods of sockets that FakeSocket doesn't support? Someone should take a look... (I'll try to give it a once-over.) 2.2.1 bugfix candidate.
* Fix SF bug 525520.Jeremy Hylton2002-03-091-20/+34
| | | | | Don't automatically add a Host: header if the headers passed to request() already has a Host key.
* SF bug report #405939: wrong Host header with proxyJeremy Hylton2002-03-081-3/+21
| | | | | | | | | | | | | | | In August, Greg said this looked good, so I'm going ahead with it. The fix is different from the one in the bug report. Instead of using a regular expression to extract the host from the url, I use urlparse.urlsplit. Martin commented that the patch doesn't address URLs that have basic authentication username and password in the header. I don't see any code anywhere in httplib that supports this feature, so I'm not going to address it for this fix. Bug fix candidate.
* The Grande 'sendall()' patch, copied from release21-maint. Fixes #516715.Martin v. Löwis2002-02-161-1/+1
| | | | | Replaces calls to socket.send() (which isn't guaranteed to send all data) with the new socket.sendall() method.
* SF #515011, cleanup: remove "or 0" conditionNeal Norwitz2002-02-111-2/+1
|
* Somebody checked in a version of httplib that doesn't even compile --Tim Peters2001-10-111-1/+1
| | | | SyntaxError. Fix it.
* Fix for SF buf #458835Jeremy Hylton2001-10-111-3/+14
| | | | | | | | | | | | | | | | | Try to be systematic about dealing with socket and ssl exceptions in FakeSocket.makefile(). The previous version of the code caught all ssl errors and treated them as EOF, even though most of the errors don't mean EOF. An SSL error can mean on of three things: 1. The SSL/TLS connection was closed. 2. The operation should be retried. 3. An error occurred. Also, if a socket error occurred and the error was EINTR, retry the call. Otherwise, it was a legitimate error and the caller should receive the exception.
View Lorry Controller Status