comparison xml/en/docs/http/websocket.xml @ 1923:66a30a380fba

Fixed links to tools.ietf.org.
author Ruslan Ermilov <ru@nginx.com>
date Mon, 06 Mar 2017 16:02:23 +0300
parents d1d49bbb3df0
children 4add6ae1296f
comparison
equal deleted inserted replaced
1922:94493c0ff5f6 1923:66a30a380fba
5 <!DOCTYPE article SYSTEM "../../../../dtd/article.dtd"> 5 <!DOCTYPE article SYSTEM "../../../../dtd/article.dtd">
6 6
7 <article name="WebSocket proxying" 7 <article name="WebSocket proxying"
8 link="/en/docs/http/websocket.html" 8 link="/en/docs/http/websocket.html"
9 lang="en" 9 lang="en"
10 rev="3"> 10 rev="4">
11 11
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="http://tools.ietf.org/html/rfc2616#section-14.42">protocol 17 the <link url="https://tools.ietf.org/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="http://tools.ietf.org/html/rfc2616#section-13.5.1">hop-by-hop</link> 23 <link url="https://tools.ietf.org/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,