Part of elisa.plugins.http_client.extern.channel_http View In Hierarchy
Known subclasses: elisa.plugins.http_client.extern.channel_http.HTTPChannelRequest, elisa.plugins.http_client.extern.client_http.HTTPClientChannelRequest
| Line # | Kind | Name | Docs |
|---|---|---|---|
| 85 | Method | __init__ | Undocumented |
| 89 | Method | lineReceived | Undocumented |
| 156 | Method | rawDataReceived | Handle incoming content. |
| 179 | Method | headerReceived | Store this header away. Check for too much header data |
| 191 | Method | allHeadersReceived | Undocumented |
| 199 | Method | allContentReceived | Undocumented |
| 205 | Method | splitConnectionHeaders | Split off connection control headers from normal headers. |
| 271 | Method | setConnectionParams | Undocumented |
| 329 | Method | abortParse | Undocumented |
| 337 | Method | pauseProducing | Undocumented |
| 341 | Method | resumeProducing | Undocumented |
| 345 | Method | stopProducing | Undocumented |
Split off connection control headers from normal headers.
The normal headers are then passed on to user-level code, while the connection headers are stashed in .connHeaders and used for things like request/response framing.
This corresponds roughly with the HTTP RFC's description of 'hop-by-hop' vs 'end-to-end' headers in RFC2616 S13.5.1, with the following exceptions: