Difference between revisions of "WebSockets"
Jump to navigation
Jump to search
↑ https://aws.amazon.com/blogs/aws/new-aws-application-load-balancer/
↑ http://nginx.org/en/CHANGES
↑ https://www.nginx.com/blog/websocket-nginx/
| (4 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
| − | [[wikipedia:WebSocket]] (2011) is a computer communications protocol, providing [[full-duplex]] communication channels over a single [[TCP]] connection. The WebSocket protocol defines a <code>ws://</code> and <code>wss://</code> prefix to indicate a WebSocket and a WebSocket Secure connection, respectively. | + | [[wikipedia:WebSocket]] (2011) is a computer communications protocol, providing [[full-duplex]] communication channels over a single [[TCP]] connection. The WebSocket protocol defines a <code>[[ws]]://</code> and <code>[[wss]]://</code> prefix to indicate a WebSocket and a WebSocket Secure connection, respectively. |
* https://developer.mozilla.org/en-US/docs/Web/API/WebSockets_API/Writing_WebSocket_client_applications | * https://developer.mozilla.org/en-US/docs/Web/API/WebSockets_API/Writing_WebSocket_client_applications | ||
| Line 16: | Line 16: | ||
* [[Server-Sent Events (SSE)]] | * [[Server-Sent Events (SSE)]] | ||
* [[Load testing]]: [[Gatling (software)]] | * [[Load testing]]: [[Gatling (software)]] | ||
| − | * [[nats.ws]] | + | * <code>[[nats.ws]]</code> |
[[curl: (1) Protocol "wss" not supported or disabled in libcurl]] | [[curl: (1) Protocol "wss" not supported or disabled in libcurl]] | ||
[[socket.io-client]] | [[socket.io-client]] | ||
| + | [[websocket handshake error: invalid value for header]] 'Upgrade' | ||
| + | * [[Caddyfile]] | ||
| + | * [[8546]] [[geth]] | ||
== See also == | == See also == | ||
Revision as of 16:18, 3 July 2024
wikipedia:WebSocket (2011) is a computer communications protocol, providing full-duplex communication channels over a single TCP connection. The WebSocket protocol defines a ws:// and wss:// prefix to indicate a WebSocket and a WebSocket Secure connection, respectively.
The URL to which to connect; this should be the URL to which the WebSocket server will respond. This should use the URL scheme wss://, although some software may allow you to use the insecure ws:// for local connections.
Web Server implementation
- Amazon ELB support WebSockets and HTTP/2 since 2016 [1]
- Nginx supports WebSockets since 2013, implemented in version 1.3.13 [2] including acting as a reverse proxy and load balancer of WebSocket applications.[3]
Related terms
curl: (1) Protocol "wss" not supported or disabled in libcurl socket.io-client websocket handshake error: invalid value for header 'Upgrade'
See also
- WebSocket, WS-RPC,
wscat, websocat, ws, wss, nats.ws, import websockets - HTTP, HTTP client, HTTP/1.1, HTTP/2, HTTP/3, HTTPS, HSTS CSR, TLS, SSL,
openSSL, WebSockets, WebRTC,ssl_certificateQUIC, HPKP, CT, List of HTTP status codes, URL redirection, Content-type:, Webhook, HTTP headers,--insecure, Axios HTTP client, HTTP cookies, HTTP ETag
Advertising:
