Tornado 6.4 Documentation
the Tornado web application will set the _xsrf cookie for all users and reject all POST, PUT, and DELETE requests that do not contain a correct _xsrf value. If you turn this setting on, you need to instrument "POST", success: function(response) { callback(eval("(" + response + ")")); }}); }; For PUT and DELETE requests (as well as POST requests that do not use form-encoded arguments), the XSRF token may also str, **kwargs: str) → None RequestHandler.post(*args: str, **kwargs: str) → None RequestHandler.delete(*args: str, **kwargs: str) → None RequestHandler.patch(*args: str, **kwargs: str) → None RequestHandler0 码力 | 268 页 | 1.09 MB | 1 年前3
Tornado 6.4 Documentation
the Tornado web application will set the _xsrf cookie for all users and reject all POST, PUT, and DELETE requests that do not contain a correct _xsrf value. If you turn this setting on, you need to instrument "POST", success: function(response) { callback(eval("(" + response + ")")); }}); }; For PUT and DELETE requests (as well as POST requests that do not use form-encoded arguments), the XSRF token may also str, **kwargs: str) → None RequestHandler.post(*args: str, **kwargs: str) → None RequestHandler.delete(*args: str, **kwargs: str) → None RequestHandler.patch(*args: str, **kwargs: str) → None RequestHandler0 码力 | 268 页 | 1.09 MB | 1 年前3
Tornado 6.4 Documentation
the Tornado web application will set the _xsrf cookie for all users and reject all POST, PUT, and DELETE requests that do not contain a correct _xsrf value. If you turn this setting on, you need to instrument "POST", success: function(response) { callback(eval("(" + response + ")")); }}); }; For PUT and DELETE requests (as well as POST requests that do not use form-encoded arguments), the XSRF token may also str, **kwargs: str) → None RequestHandler.post(*args: str, **kwargs: str) → None RequestHandler.delete(*args: str, **kwargs: str) → None RequestHandler.patch(*args: str, **kwargs: str) → None RequestHandler0 码力 | 268 页 | 1.09 MB | 1 年前3
Tornado 6.3 Documentation
the Tornado web application will set the _xsrf cookie for all users and reject all POST, PUT, and DELETE requests that do not contain a correct _xsrf value. If you turn this setting on, you need to instrument "POST", success: function(response) { callback(eval("(" + response + ")")); }}); }; For PUT and DELETE requests (as well as POST requests that do not use form-encoded arguments), the XSRF token may also str, **kwargs: str) → None RequestHandler.post(*args: str, **kwargs: str) → None RequestHandler.delete(*args: str, **kwargs: str) → None RequestHandler.patch(*args: str, **kwargs: str) → None RequestHandler0 码力 | 264 页 | 1.06 MB | 1 年前3
Tornado 6.5 Documentationthe Tornado web application will set the _xsrf cookie for all users and reject all POST, PUT, and DELETE requests that do not contain a correct _xsrf value. If you turn this setting on, you need to instrument "POST", success: function(response) { callback(eval("(" + response + ")")); }}); }; For PUT and DELETE requests (as well as POST requests that do not use form-encoded arguments), the XSRF token may also str, **kwargs: str) → None RequestHandler.post(*args: str, **kwargs: str) → None RequestHandler.delete(*args: str, **kwargs: str) → None RequestHandler.patch(*args: str, **kwargs: str) → None RequestHandler0 码力 | 272 页 | 1.12 MB | 3 月前3
Tornado 6.4 Documentation
the Tornado web application will set the _xsrf cookie for all users and reject all POST, PUT, and DELETE requests that do not contain a correct _xsrf value. If you turn this setting on, you need to instrument success: function(response) { callback(eval("(" + response + ")")); }}); }; For PUT and DELETE requests (as well as POST requests that do not use form-encoded arguments), the XSRF token may also RequestHandler.on_finish() RequestHandler.get() RequestHandler.head() RequestHandler.post() RequestHandler.delete() RequestHandler.patch() RequestHandler.put() RequestHandler.options() Input RequestHandler.get_argument()0 码力 | 432 页 | 402.58 KB | 1 年前3
Tornado 6.4 Documentation
the Tornado web application will set the _xsrf cookie for all users and reject all POST, PUT, and DELETE requests that do not contain a correct _xsrf value. If you turn this setting on, you need to instrument success: function(response) { callback(eval("(" + response + ")")); }}); }; For PUT and DELETE requests (as well as POST requests that do not use form-encoded arguments), the XSRF token may also RequestHandler.on_finish() RequestHandler.get() RequestHandler.head() RequestHandler.post() RequestHandler.delete() RequestHandler.patch() RequestHandler.put() RequestHandler.options() Input RequestHandler.get_argument()0 码力 | 432 页 | 402.58 KB | 1 年前3
Tornado 6.4 Documentation
the Tornado web application will set the _xsrf cookie for all users and reject all POST, PUT, and DELETE requests that do not contain a correct _xsrf value. If you turn this setting on, you need to instrument success: function(response) { callback(eval("(" + response + ")")); }}); }; For PUT and DELETE requests (as well as POST requests that do not use form-encoded arguments), the XSRF token may also RequestHandler.on_finish() RequestHandler.get() RequestHandler.head() RequestHandler.post() RequestHandler.delete() RequestHandler.patch() RequestHandler.put() RequestHandler.options() Input RequestHandler.get_argument()0 码力 | 432 页 | 402.58 KB | 1 年前3
Tornado 6.3 Documentation
the Tornado web application will set the _xsrf cookie for all users and reject all POST, PUT, and DELETE requests that do not contain a correct _xsrf value. If you turn this setting on, you need to instrument success: function(response) { callback(eval("(" + response + ")")); }}); }; For PUT and DELETE requests (as well as POST requests that do not use form-encoded arguments), the XSRF token may also RequestHandler.on_finish() RequestHandler.get() RequestHandler.head() RequestHandler.post() RequestHandler.delete() RequestHandler.patch() RequestHandler.put() RequestHandler.options() Input RequestHandler.get_argument()0 码力 | 423 页 | 398.18 KB | 1 年前3
Tornado 6.5 Documentationthe Tornado web application will set the _xsrf cookie for all users and reject all POST, PUT, and DELETE requests that do not contain a correct _xsrf value. If you turn this setting on, you need to instrument success: function(response) { callback(eval("(" + response + ")")); }}); }; For PUT and DELETE requests (as well as POST requests that do not use form-encoded arguments), the XSRF token may also RequestHandler.on_finish() RequestHandler.get() RequestHandler.head() RequestHandler.post() RequestHandler.delete() RequestHandler.patch() RequestHandler.put() RequestHandler.options() Input RequestHandler.get_argument()0 码力 | 437 页 | 405.14 KB | 3 月前3
共 20 条
- 1
- 2













