Mercurial > hg > nginx-site
comparison xml/en/docs/http/websocket.xml @ 2831:4add6ae1296f
Updated links to datatracker.ietf.org.
author | Sergey Kandaurov <pluknet@nginx.com> |
---|---|
date | Wed, 26 Jan 2022 16:26:47 +0300 |
parents | 66a30a380fba |
children |
comparison
equal
deleted
inserted
replaced
2830:419b081fd2fa | 2831:4add6ae1296f |
---|---|
12 | 12 |
13 <section> | 13 <section> |
14 | 14 |
15 <para> | 15 <para> |
16 To turn a connection between a client and server from HTTP/1.1 into WebSocket, | 16 To turn a connection between a client and server from HTTP/1.1 into WebSocket, |
17 the <link url="https://tools.ietf.org/html/rfc2616#section-14.42">protocol | 17 the <link url="https://datatracker.ietf.org/doc/html/rfc2616#section-14.42">protocol |
18 switch</link> mechanism available in HTTP/1.1 is used. | 18 switch</link> mechanism available in HTTP/1.1 is used. |
19 </para> | 19 </para> |
20 | 20 |
21 <para> | 21 <para> |
22 There is one subtlety however: since the <header>Upgrade</header> is a | 22 There is one subtlety however: since the <header>Upgrade</header> is a |
23 <link url="https://tools.ietf.org/html/rfc2616#section-13.5.1">hop-by-hop</link> | 23 <link url="https://datatracker.ietf.org/doc/html/rfc2616#section-13.5.1">hop-by-hop</link> |
24 header, it is not passed from a client to proxied server. | 24 header, it is not passed from a client to proxied server. |
25 With forward proxying, clients may use the <literal>CONNECT</literal> | 25 With forward proxying, clients may use the <literal>CONNECT</literal> |
26 method to circumvent this issue. | 26 method to circumvent this issue. |
27 This does not work with reverse proxying however, | 27 This does not work with reverse proxying however, |
28 since clients are not aware of any proxy servers, | 28 since clients are not aware of any proxy servers, |