Falcon v3.1.1-b3 DocumentationSupported HTTP methods are those specified in RFC 7231 and RFC 5789. This includes GET, HEAD, POST, PUT, DELETE, CONNECT, OPTIONS, TRACE, and PATCH. We call these well-known methods “responders”. Each responder that starts with on_ and ends in the lowercased HTTP method name (e.g., on_get(), on_patch(), on_delete(), etc.) Note: If a Python method is omitted for a given HTTP verb, the framework will automatically Release 3.1.1b3 import msgpack class RedisCache: PREFIX = 'asgilook:' INVALIDATE_ON = frozenset({'DELETE', 'POST', 'PUT'}) CACHE_HEADER = 'X-ASGILook-Cache' TTL = 3600 def __init__(self, config): self0 码力 | 378 页 | 1.29 MB | 1 年前3
Falcon v3.1.1-b1 DocumentationSupported HTTP methods are those specified in RFC 7231 and RFC 5789. This includes GET, HEAD, POST, PUT, DELETE, CONNECT, OPTIONS, TRACE, and PATCH. We call these well-known methods “responders”. Each responder that starts with on_ and ends in the lowercased HTTP method name (e.g., on_get(), on_patch(), on_delete(), etc.) Note: If a Python method is omitted for a given HTTP verb, the framework will automatically Release 3.1.1b1 import msgpack class RedisCache: PREFIX = 'asgilook:' INVALIDATE_ON = frozenset({'DELETE', 'POST', 'PUT'}) CACHE_HEADER = 'X-ASGILook-Cache' TTL = 3600 def __init__(self, config): self0 码力 | 378 页 | 1.29 MB | 1 年前3
Falcon v3.1.1-a DocumentationSupported HTTP methods are those specified in RFC 7231 and RFC 5789. This includes GET, HEAD, POST, PUT, DELETE, CONNECT, OPTIONS, TRACE, and PATCH. We call these well-known methods “responders”. Each responder that starts with on_ and ends in the lowercased HTTP method name (e.g., on_get(), on_patch(), on_delete(), etc.) Note: If a Python method is omitted for a given HTTP verb, the framework will automatically Release 3.1.1 import msgpack class RedisCache: PREFIX = 'asgilook:' INVALIDATE_ON = frozenset({'DELETE', 'POST', 'PUT'}) CACHE_HEADER = 'X-ASGILook-Cache' TTL = 3600 def __init__(self, config): self0 码力 | 378 页 | 1.29 MB | 1 年前3
Falcon v3.1.0 DocumentationSupported HTTP methods are those specified in RFC 7231 and RFC 5789. This includes GET, HEAD, POST, PUT, DELETE, CONNECT, OPTIONS, TRACE, and PATCH. We call these well-known methods “responders”. Each responder that starts with on_ and ends in the lowercased HTTP method name (e.g., on_get(), on_patch(), on_delete(), etc.) Note: If a Python method is omitted for a given HTTP verb, the framework will automatically Release 3.1.0 import msgpack class RedisCache: PREFIX = 'asgilook:' INVALIDATE_ON = frozenset({'DELETE', 'POST', 'PUT'}) CACHE_HEADER = 'X-ASGILook-Cache' TTL = 3600 def __init__(self, config): self0 码力 | 362 页 | 1.29 MB | 1 年前3
Falcon v3.1.1 DocumentationSupported HTTP methods are those specified in RFC 7231 and RFC 5789. This includes GET, HEAD, POST, PUT, DELETE, CONNECT, OPTIONS, TRACE, and PATCH. We call these well-known methods “responders”. Each responder that starts with on_ and ends in the lowercased HTTP method name (e.g., on_get(), on_patch(), on_delete(), etc.) Note: If a Python method is omitted for a given HTTP verb, the framework will automatically Release 3.1.1 import msgpack class RedisCache: PREFIX = 'asgilook:' INVALIDATE_ON = frozenset({'DELETE', 'POST', 'PUT'}) CACHE_HEADER = 'X-ASGILook-Cache' TTL = 3600 def __init__(self, config): self0 码力 | 378 页 | 1.29 MB | 1 年前3
Falcon v3.1.1-rc1 DocumentationSupported HTTP methods are those specified in RFC 7231 and RFC 5789. This includes GET, HEAD, POST, PUT, DELETE, CONNECT, OPTIONS, TRACE, and PATCH. We call these well-known methods “responders”. Each responder that starts with on_ and ends in the lowercased HTTP method name (e.g., on_get(), on_patch(), on_delete(), etc.) Note: If a Python method is omitted for a given HTTP verb, the framework will automatically Release 3.1.1rc1 import msgpack class RedisCache: PREFIX = 'asgilook:' INVALIDATE_ON = frozenset({'DELETE', 'POST', 'PUT'}) CACHE_HEADER = 'X-ASGILook-Cache' TTL = 3600 def __init__(self, config): self0 码力 | 378 页 | 1.29 MB | 1 年前3
Falcon v3.0.0-b2 DocumentationSupported HTTP methods are those specified in RFC 7231 and RFC 5789. This includes GET, HEAD, POST, PUT, DELETE, CONNECT, OPTIONS, TRACE, and PATCH. We call these well-known methods “responders”. Each responder that starts with on_ and ends in the lowercased HTTP method name (e.g., on_get(), on_patch(), on_delete(), etc.) Note: If a Python method is omitted for a given HTTP verb, the framework will automatically (continued from previous page) class RedisCache: PREFIX = 'asgilook:' INVALIDATE_ON = frozenset({'DELETE', 'POST', 'PUT'}) CACHE_HEADER = 'X-ASGILook-Cache' TTL = 3600 def __init__(self, config): self0 码力 | 340 页 | 1.15 MB | 1 年前3
Falcon v3.0.0 DocumentationSupported HTTP methods are those specified in RFC 7231 and RFC 5789. This includes GET, HEAD, POST, PUT, DELETE, CONNECT, OPTIONS, TRACE, and PATCH. We call these well-known methods “responders”. Each responder that starts with on_ and ends in the lowercased HTTP method name (e.g., on_get(), on_patch(), on_delete(), etc.) Note: If a Python method is omitted for a given HTTP verb, the framework will automatically (continued from previous page) class RedisCache: PREFIX = 'asgilook:' INVALIDATE_ON = frozenset({'DELETE', 'POST', 'PUT'}) CACHE_HEADER = 'X-ASGILook-Cache' TTL = 3600 def __init__(self, config): self0 码力 | 344 页 | 1.16 MB | 1 年前3
Falcon v3.0.1 DocumentationSupported HTTP methods are those specified in RFC 7231 and RFC 5789. This includes GET, HEAD, POST, PUT, DELETE, CONNECT, OPTIONS, TRACE, and PATCH. We call these well-known methods “responders”. Each responder that starts with on_ and ends in the lowercased HTTP method name (e.g., on_get(), on_patch(), on_delete(), etc.) Note: If a Python method is omitted for a given HTTP verb, the framework will automatically (continued from previous page) class RedisCache: PREFIX = 'asgilook:' INVALIDATE_ON = frozenset({'DELETE', 'POST', 'PUT'}) CACHE_HEADER = 'X-ASGILook-Cache' TTL = 3600 def __init__(self, config): self0 码力 | 344 页 | 1.16 MB | 1 年前3
Falcon v3.0.0-b1 DocumentationSupported HTTP methods are those specified in RFC 7231 and RFC 5789. This includes GET, HEAD, POST, PUT, DELETE, CONNECT, OPTIONS, TRACE, and PATCH. We call these well-known methods “responders”. Each responder could look like: import msgpack class RedisCache: PREFIX = 'asgilook:' INVALIDATE_ON = frozenset({'DELETE', 'POST', 'PUT'}) CACHE_HEADER = 'X-ASGILook-Cache' TTL = 3600 def __init__(self, config): self return key = f'{self.PREFIX}/{req.path}' if req.method in self.INVALIDATE_ON: await self._redis.delete(key) elif not resp.context.cached: data = await self._serialize_response(resp) await self._redis0 码力 | 338 页 | 1.14 MB | 1 年前3
共 40 条
- 1
- 2
- 3
- 4













