Tornado 4.5 Documentation
secure websocket connection (wss://) with a self-signed certificate, the connection from a browser may fail because it wants to show the “accept this certificate” dialog but has nowhere to show it. You must must first visit a regular HTML page using the same certificate to accept it before the websocket connection will succeed. If the application setting websocket_ping_interval has a non-zero value, a ping proxy_username=None, proxy_password=None, proxy_auth_mode=None, allow_nonstandard_methods=None, validate_cert=None, ca_certs=None, allow_ipv6=None, client_key=None, client_cert=None, body_producer=None, expect_100_continue=False0 码力 | 333 页 | 322.34 KB | 1 年前3
Tornado 6.1 Documentation
Applications that use TLS are not vulnerable to this attack (because the browser will display certificate mismatch warnings that block automated access to the target site). Applications that cannot use secure websocket connection (wss://) with a self-signed certificate, the connection from a browser may fail because it wants to show the “accept this certificate” dialog but has nowhere to show it. You must must first visit a regular HTML page using the same certificate to accept it before the websocket connection will succeed. If the application setting websocket_ping_interval has a non-zero value, a ping0 码力 | 245 页 | 904.24 KB | 1 年前3
Tornado 5.1 Documentation
Applications that use TLS are not vulnerable to this attack (because the browser will display certificate mismatch warnings that block automated access to the target site). Applications that cannot use secure websocket connection (wss://) with a self-signed certificate, the connection from a browser may fail because it wants to show the “accept this certificate” dialog but has nowhere to show it. You must must first visit a regular HTML page using the same certificate to accept it before the websocket connection will succeed. If the application setting websocket_ping_interval has a non-zero value, a ping0 码力 | 243 页 | 895.80 KB | 1 年前3
Tornado 6.0 Documentation
Applications that use TLS are not vulnerable to this attack (because the browser will display certificate mismatch warnings that block automated access to the target site). Applications that cannot use secure websocket connection (wss://) with a self-signed certificate, the connection from a browser may fail because it wants to show the “accept this certificate” dialog but has nowhere to show it. You must must first visit a regular HTML page using the same certificate to accept it before the websocket connection will succeed. If the application setting websocket_ping_interval has a non-zero value, a ping0 码力 | 245 页 | 885.76 KB | 1 年前3
Tornado 4.5 Documentation
secure websocket connection (wss://) with a self-signed certificate, the connection from a browser may fail because it wants to show the “accept this certificate” dialog but has nowhere to show it. You must must first visit a regular HTML page using the same certificate to accept it before the websocket connection will succeed. If the application setting websocket_ping_interval has a non-zero value, a ping proxy_username=None, proxy_password=None, proxy_auth_mode=None, allow_nonstandard_methods=None, val- idate_cert=None, ca_certs=None, al- low_ipv6=None, client_key=None, client_cert=None, body_producer=None, expect_100_continue=False0 码力 | 222 页 | 833.04 KB | 1 年前3
Tornado 6.4 Documentation
Applications that use TLS are not vulnerable to this attack (because the browser will display certificate mismatch warnings that block automated access to the target site). Applications that cannot use secure websocket connection (wss://) with a self-signed certificate, the connection from a browser may fail because it wants to show the “accept this certificate” dialog but has nowhere to show it. You must must first visit a regular HTML page using the same certificate to accept it before the websocket connection will succeed. If the application setting websocket_ping_interval has a non-zero value, a ping0 码力 | 268 页 | 1.09 MB | 1 年前3
Tornado 6.2 Documentation
Applications that use TLS are not vulnerable to this attack (because the browser will display certificate mismatch warnings that block automated access to the target site). Applications that cannot use secure websocket connection (wss://) with a self-signed certificate, the connection from a browser may fail because it wants to show the “accept this certificate” dialog but has nowhere to show it. You must must first visit a regular HTML page using the same certificate to accept it before the websocket connection will succeed. If the application setting websocket_ping_interval has a non-zero value, a ping0 码力 | 260 页 | 1.06 MB | 1 年前3
Tornado 6.4 Documentation
Applications that use TLS are not vulnerable to this attack (because the browser will display certificate mismatch warnings that block automated access to the target site). Applications that cannot use secure websocket connection (wss://) with a self-signed certificate, the connection from a browser may fail because it wants to show the “accept this certificate” dialog but has nowhere to show it. You must must first visit a regular HTML page using the same certificate to accept it before the websocket connection will succeed. If the application setting websocket_ping_interval has a non-zero value, a ping0 码力 | 268 页 | 1.09 MB | 1 年前3
Tornado 6.4 Documentation
Applications that use TLS are not vulnerable to this attack (because the browser will display certificate mismatch warnings that block automated access to the target site). Applications that cannot use secure websocket connection (wss://) with a self-signed certificate, the connection from a browser may fail because it wants to show the “accept this certificate” dialog but has nowhere to show it. You must must first visit a regular HTML page using the same certificate to accept it before the websocket connection will succeed. If the application setting websocket_ping_interval has a non-zero value, a ping0 码力 | 268 页 | 1.09 MB | 1 年前3
Tornado 6.3 Documentation
Applications that use TLS are not vulnerable to this attack (because the browser will display certificate mismatch warnings that block automated access to the target site). Applications that cannot use secure websocket connection (wss://) with a self-signed certificate, the connection from a browser may fail because it wants to show the “accept this certificate” dialog but has nowhere to show it. You must must first visit a regular HTML page using the same certificate to accept it before the websocket connection will succeed. If the application setting websocket_ping_interval has a non-zero value, a ping0 码力 | 264 页 | 1.06 MB | 1 年前3
共 20 条
- 1
- 2













