18.6.1 Request Objects
The following methods describe all of Request's public interface, and so all must be overridden in subclasses.
-
Set the Request data to data. This is ignored by all
handlers except HTTP handlers -- and there it should be a byte
string, and will change the request to be
POST
rather thanGET
.
-
Return a string indicating the HTTP request method. This is only
meaningful for HTTP requests, and currently always returns
'GET'
or'POST'
.
-
Return whether the instance has a non-
None
data.
- Return the instance's data.
- Add another header to the request. Headers are currently ignored by all handlers except HTTP handlers, where they are added to the list of headers sent to the server. Note that there cannot be more than one header with the same name, and later calls will overwrite previous calls in case the key collides. Currently, this is no loss of HTTP functionality, since all headers which have meaning when used more than once have a (header-specific) way of gaining the same functionality using only one header.
- Add a header that will not be added to a redirected request. New in version 2.4.
- Return whether the instance has the named header (checks both regular and unredirected). New in version 2.4.
- Return the URL given in the constructor.
- Return the type of the URL -- also known as the scheme.
- Return the host to which a connection will be made.
- Return the selector -- the part of the URL that is sent to the server.
- Prepare the request by connecting to a proxy server. The host and type will replace those of the instance, and the instance's selector will be the original URL given in the constructor.
- Return the request-host of the origin transaction, as defined by RFC 2965. See the documentation for the Request constructor.
- Return whether the request is unverifiable, as defined by RFC 2965. See the documentation for the Request constructor.
See About this document... for information on suggesting changes.