• Home
  • Raw
  • Download

Lines Matching +full:url +full:- +full:connection +full:- +full:client

5 lws is able to use a mount to place reverse proxies into the URL space.
9 server process and integrate the result into a coherent URL namespace on
12 ![overview](../doc-assets/http-proxy-overview.svg)
17 the actual public-facing web server. The unix domain socket server may
20 Compared to CGI, there are no forks to make a connection to the unix
31 url space.
44 http/1.1. That implies `transfer-encoding: chunking` in the case that the
48 translating between h1 and h2 header formats if the return connection is
51 The h1 onward proxy connection translates the following headers from the return
52 connection, which may be h1 or h2:
55 ---|---
57 etag|Information on any etag the client has cached for this URI
58 if-modified-since|Information on the freshness of any etag the client has cached for this URI
59 accept-language|Which languages the return path client prefers
60 accept-encoding|Which compression encodings the client can accept
61 cache-control|Information from the return path client about cache acceptability
62 x-forwarded-for|The IP address of the return path client
64 This implies that the proxied connection can
66 - return 301 etc to say the return path client's etag is still valid
68 - choose to compress using an acceptable content-encoding
71 connection (always h1) back to the return path (which may be h1 or h2)
74 ---|---
75 content-length|If present, an assertion of how much payload is expected
76 content-type|The mimetype of the payload
78 accept-language|This is returned to the return path client because there is no easy way for the ret…
79 content-encoding|Any compression format on the payload (selected from what the client sent in accep…
80 cache-control|The onward server's response about cacheability of its payload
82 ### h1 -> h2 conversion
84 Chunked encoding that may have been used on the outgoing proxy client connection
87 Headers are converted to all lower-case and hpack format for h2 return connections.
89 Header and payload proxying is staged according to when the return connection
96 `HTTP_STATUS_SERVICE_UNAVAILABLE` along with a brief human-readable explanation.