Tornado 6.0 Documentation
custom HTTP header named X-XSRFToken or X-CSRFToken (the latter is accepted for compatibility with Django). See http://en.wikipedia.org/wiki/Cross-site_request_forgery Changed in version 3.2.2: Added support RequestHandlers and WSGI in the same server. Typical usage: wsgi_app = tornado.wsgi.WSGIContainer( django.core.handlers.wsgi.WSGIHandler()) application = tornado.web.Application([ (r"/foo", FooHandler) cookie-related RFCs (because browsers don’t either). The algorithm used is identical to that used by Django version 1.9.10. New in version 4.4.2. Parameters: tornado.http1connection – HTTP/1.x client/server0 码力 | 869 页 | 692.83 KB | 1 年前3Tornado 6.1 Documentation
custom HTTP header named X-XSRFToken or X-CSRFToken (the latter is accepted for compatibility with Django). See http://en.wikipedia.org/wiki/Cross-site_request_forgery Changed in version 3.2.2: Added support RequestHandlers and WSGI in the same server. Typical usage: wsgi_app = tornado.wsgi.WSGIContainer( django.core.handlers.wsgi.WSGIHandler()) application = tornado.web.Application([ (r"/foo", FooHandler) cookie-related RFCs (because browsers don’t either). The algorithm used is identical to that used by Django version 1.9.10. New in version 4.4.2. Parameters: tornado.http1connection – HTTP/1.x client/server0 码力 | 931 页 | 708.03 KB | 1 年前3Tornado 4.5 Documentation
custom HTTP header named X-XSRFToken or X-CSRFToken (the latter is accepted for compatibility with Django). See http://en.wikipedia.org/wiki/Cross-site_request_forgery Prior to release 1.1.1, this check RequestHandlers and WSGI in the same server. Typical usage: wsgi_app = tornado.wsgi.WSGIContainer( django.core.handlers.wsgi.WSGIHandler()) application = tornado.web.Application([ (r"/foo", FooHandler) cookie-related RFCs (because browsers don’t either). The algorithm used is identical to that used by Django version 1.9.10. New in version 4.4.2. Parameters: tornado.http1connection – HTTP/1.x client/server0 码力 | 333 页 | 322.34 KB | 1 年前3Tornado 4.5 Documentation
custom HTTP header named X-XSRFToken or X-CSRFToken (the latter is accepted for compatibility with Django). See http://en.wikipedia.org/wiki/Cross-site_request_forgery Prior to release 1.1.1, this check RequestHandlers and WSGI in the same server. Typical usage: wsgi_app = tornado.wsgi.WSGIContainer( django.core.handlers.wsgi.WSGIHandler()) application = tornado.web.Application([ (r"/foo", FooHandler), cookie-related RFCs (because browsers don’t either). The algorithm used is identical to that used by Django version 1.9.10. New in version 4.4.2. 4.3.4 tornado.http1connection – HTTP/1.x client/server implementation0 码力 | 222 页 | 833.04 KB | 1 年前3Tornado 5.1 Documentation
custom HTTP header named X-XSRFToken or X-CSRFToken (the latter is accepted for compatibility with Django). See http://en.wikipedia.org/wiki/Cross-site_request_forgery Prior to release 1.1.1, this check RequestHandlers and WSGI in the same server. Typical usage: wsgi_app = tornado.wsgi.WSGIContainer( django.core.handlers.wsgi.WSGIHandler()) application = tornado.web.Application([ (r"/foo", FooHandler), cookie-related RFCs (because browsers don’t either). The algorithm used is identical to that used by Django version 1.9.10. New in version 4.4.2. 5.3.4 tornado.http1connection – HTTP/1.x client/server implementation0 码力 | 243 页 | 895.80 KB | 1 年前3Tornado 5.1 Documentation
custom HTTP header named X-XSRFToken or X-CSRFToken (the latter is accepted for compatibility with Django). See http://en.wikipedia.org/wiki/Cross-site_request_forgery Prior to release 1.1.1, this check RequestHandlers and WSGI in the same server. Typical usage: wsgi_app = tornado.wsgi.WSGIContainer( django.core.handlers.wsgi.WSGIHandler()) application = tornado.web.Application([ (r"/foo", FooHandler) cookie-related RFCs (because browsers don’t either). The algorithm used is identical to that used by Django version 1.9.10. New in version 4.4.2. Parameters: tornado.http1connection – HTTP/1.x client/server0 码力 | 359 页 | 347.32 KB | 1 年前3Tornado 6.1 Documentation
custom HTTP header named X-XSRFToken or X-CSRFToken (the latter is accepted for compatibility with Django). See http://en.wikipedia.org/wiki/Cross-site_request_forgery Changed in version 3.2.2: Added support RequestHandlers and WSGI in the same server. Typical usage: wsgi_app = tornado.wsgi.WSGIContainer( django.core.handlers.wsgi.WSGIHandler()) application = tornado.web.Application([ (r"/foo", FooHandler), cookie-related RFCs (because browsers don’t either). The algorithm used is identical to that used by Django version 1.9.10. New in version 4.4.2. 6.3.4 tornado.http1connection – HTTP/1.x client/server implementation0 码力 | 245 页 | 904.24 KB | 1 年前3Tornado 6.0 Documentation
custom HTTP header named X-XSRFToken or X-CSRFToken (the latter is accepted for compatibility with Django). See http://en.wikipedia.org/wiki/Cross-site_request_forgery Changed in version 3.2.2: Added support RequestHandlers and WSGI in the same server. Typical usage: wsgi_app = tornado.wsgi.WSGIContainer( django.core.handlers.wsgi.WSGIHandler()) application = tornado.web.Application([ (r"/foo", FooHandler), cookie-related RFCs (because browsers don’t either). The algorithm used is identical to that used by Django version 1.9.10. New in version 4.4.2. 94 Chapter 6. Documentation Tornado Documentation, Release0 码力 | 245 页 | 885.76 KB | 1 年前3Tornado 6.2 Documentation
custom HTTP header named X-XSRFToken or X-CSRFToken (the latter is accepted for compatibility with Django). See http://en.wikipedia.org/wiki/Cross-site_request_forgery Changed in version 3.2.2: Added support RequestHandlers and WSGI in the same server. Typical usage: wsgi_app = tornado.wsgi.WSGIContainer( django.core.handlers.wsgi.WSGIHandler()) application = tornado.web.Application([ (r"/foo", FooHandler), cookie-related RFCs (because browsers don’t either). The algorithm used is identical to that used by Django version 1.9.10. New in version 4.4.2. 6.3.4 tornado.http1connection – HTTP/1.x client/server implementation0 码力 | 260 页 | 1.06 MB | 1 年前3Tornado 6.2 Documentation
custom HTTP header named X-XSRFToken or X-CSRFToken (the latter is accepted for compatibility with Django). See http://en.wikipedia.org/wiki/Cross-site_request_forgery Changed in version 3.2.2: Added support RequestHandlers and WSGI in the same server. Typical usage: wsgi_app = tornado.wsgi.WSGIContainer( django.core.handlers.wsgi.WSGIHandler()) application = tornado.web.Application([ (r"/foo", FooHandler) cookie-related RFCs (because browsers don’t either). The algorithm used is identical to that used by Django version 1.9.10. New in version 4.4.2. Parameters: tornado.http1connection – HTTP/1.x client/server0 码力 | 407 页 | 385.03 KB | 1 年前3
共 20 条
- 1
- 2