Falcon v1.2.0 Documentationwell-defined signature so that you can host the application with any web server that understands the WSGI protocol [http://legacy.python.org/dev/peps/pep-3333/]. Next let’s take a look at the falcon.API class (dict) – Set of global options passed from the API handler. scheme str – Either ‘http’ or ‘https’. protocol str – Deprecated alias for scheme. Will be removed in a future release. method str – HTTP method path='/', query_string=None, headers=None, body=None, file_wrapper=None, params=None, params_csv=True, protocol='http') Simulates a request to a WSGI application. Performs a request against a WSGI application0 码力 | 177 页 | 252.56 KB | 1 年前3
Falcon v1.2.0 Documentationwell-defined signature so that you can host the application with any web server that understands the WSGI protocol. Next let’s take a look at the falcon.API class. Install IPython and fire it up: $ pip install (dict) – Set of global options passed from the API handler. scheme str – Either ‘http’ or ‘https’. protocol str – Deprecated alias for scheme. Will be removed in a future release. method str – HTTP method query_string=None, head- ers=None, body=None, file_wrapper=None, params=None, params_csv=True, protocol=’http’) Simulates a request to a WSGI application. 106 Chapter 6. Documentation Falcon Documentation0 码力 | 134 页 | 498.46 KB | 1 年前3
Falcon v1.3.0 Documentationwell-defined signature so that you can host the application with any web server that understands the WSGI protocol [http://legacy.python.org/dev/peps/pep-3333/]. Next let’s take a look at the falcon.API class returned instead. (See also: RFC 7239, Section 1 [https://tools.ietf.org/html/rfc7239#section-1]) protocol str – Deprecated alias for scheme. Will be removed in a future release. method str – HTTP method scheme str – The value of the “proto” parameter, or None if the parameter is absent. Indicates the protocol that was used to make the request to the proxy. Response class falcon.Response(options=None)0 码力 | 194 页 | 266.90 KB | 1 年前3
Falcon v3.0.0 Documentationwith more optimized alternatives such as uvloop (a faster event loop), httptools (a faster HTTP protocol implementation) etc: $ pip install uvicorn[standard] See also a longer explanation on Uvicorn’s “traditional”, synchronous flavor of Falcon using the WSGI [https://www.python.org/dev/peps/pep-3333/] protocol. Developing an async application? Check out our ASGI tutorial instead! First Steps The first well-defined signature so that you can host the application with any web server that understands the WSGI protocol [http://legacy.python.org/dev/peps/pep-3333/]. Next let’s take a look at the falcon.App class0 码力 | 1055 页 | 739.30 KB | 1 年前3
Falcon v3.0.1 Documentationwith more optimized alternatives such as uvloop (a faster event loop), httptools (a faster HTTP protocol implementation) etc: $ pip install uvicorn[standard] See also a longer explanation on Uvicorn’s “traditional”, synchronous flavor of Falcon using the WSGI [https://www.python.org/dev/peps/pep-3333/] protocol. Developing an async application? Check out our ASGI tutorial instead! First Steps The first well-defined signature so that you can host the application with any web server that understands the WSGI protocol [http://legacy.python.org/dev/peps/pep-3333/]. Next let’s take a look at the falcon.App class0 码力 | 1058 页 | 741.59 KB | 1 年前3
Falcon v3.0.0-b2 Documentationwith more optimized alternatives such as uvloop (a faster event loop), httptools (a faster HTTP protocol implementation) etc: $ pip install uvicorn[standard] See also a longer explanation on Uvicorn’s “traditional”, synchronous flavor of Falcon using the WSGI [https://www.python.org/dev/peps/pep-3333/] protocol. Developing an async application? Check out our ASGI tutorial instead! First Steps The first well-defined signature so that you can host the application with any web server that understands the WSGI protocol [http://legacy.python.org/dev/peps/pep-3333/]. Next let’s take a look at the falcon.App class0 码力 | 1041 页 | 730.21 KB | 1 年前3
Guzzle PHP v5 Documentationduration of the timeout. HTTP_PROXY Defines the proxy to use when sending requests using the “http” protocol. 12 Chapter 1. User Guide Guzzle, Release Note: because the HTTP_PROXY variable may contain arbitrary more information. HTTPS_PROXY Defines the proxy to use when sending requests using the “https” protocol. Relevant ini Settings Guzzle can utilize PHP ini settings when configuring clients. openssl HTTP handlers to use only ipv4 protocol or “v6” for ipv6 protocol. Types string Default null Constant GuzzleHttp\RequestOptions::FORCE_IP_RESOLVE // Force ipv4 protocol $client->request('GET', '/foo'0 码力 | 49 页 | 231.08 KB | 11 月前3
Guzzle PHP 6.5 Documentationduration of the timeout. HTTP_PROXY Defines the proxy to use when sending requests using the "http" protocol. Note: because the HTTP_PROXY variable may contain arbitrary user input on some (CGI) environments more information. HTTPS_PROXY Defines the proxy to use when sending requests using the "https" protocol. NO_PROXY Defines URLs for which a proxy should not be used. See proxy for usage. Relevant ini HTTP handlers to use only ipv4 protocol or "v6" for ipv6 protocol. Types string Default null Constant GuzzleHttp\RequestOptions::FORCE_IP_RESOLVE // Force ipv4 protocol $client->request('GET', '/foo'0 码力 | 65 页 | 311.42 KB | 11 月前3
Guzzle PHP 7.0 Documentationduration of the timeout. HTTP_PROXY Defines the proxy to use when sending requests using the "http" protocol. Note: because the HTTP_PROXY variable may contain arbitrary user input on some (CGI) environments more information. HTTPS_PROXY Defines the proxy to use when sending requests using the "https" protocol. NO_PROXY Defines URLs for which a proxy should not be used. See proxy for usage. Relevant ini HTTP handlers to use only ipv4 protocol or "v6" for ipv6 protocol. Types string Default null Constant GuzzleHttp\RequestOptions::FORCE_IP_RESOLVE // Force ipv4 protocol $client->request('GET', '/foo'0 码力 | 64 页 | 310.93 KB | 11 月前3
Guzzle PHP 7.0 Documentationduration of the timeout. HTTP_PROXY Defines the proxy to use when sending requests using the “http” protocol. Note: because the HTTP_PROXY variable may contain arbitrary user input on some (CGI) environments more information. HTTPS_PROXY Defines the proxy to use when sending requests using the “https” protocol. NO_PROXY Defines URLs for which a proxy should not be used. See proxy for usage. 1.2. Quickstart HTTP handlers to use only ipv4 protocol or “v6” for ipv6 protocol. Types string Default null Constant GuzzleHttp\RequestOptions::FORCE_IP_RESOLVE // Force ipv4 protocol $client->request('GET', '/foo'0 码力 | 50 页 | 235.39 KB | 11 月前3
共 68 条
- 1
- 2
- 3
- 4
- 5
- 6
- 7













