Many hyperlinks are disabled.
Use anonymous login
to enable hyperlinks.
Overview
| Comment: | Typos and minor enhancements to the althttpd.md document. |
|---|---|
| Downloads: | Tarball | ZIP archive | SQL archive |
| Timelines: | family | ancestors | descendants | both | trunk |
| Files: | files | file ages | folders |
| SHA3-256: |
5140eb346c4d17cca0ad3e10270cc26d |
| User & Date: | drh 2019-10-02 10:40:53 |
Context
|
2019-10-02
| ||
| 11:41 | Merge branch-3.29 enhancements into trunk, and in particular the hd_adunit change. (check-in: caa36aeea0 user: drh tags: trunk) | |
| 10:40 | Typos and minor enhancements to the althttpd.md document. (check-in: 5140eb346c user: drh tags: trunk) | |
|
2019-09-28
| ||
| 19:02 | Typo fixes. (check-in: 7a37431be5 user: drh tags: trunk) | |
Changes
Changes to misc/althttpd.md.
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
...
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
|
itself listens on port 80 for incoming HTTP requests, then forks a copy of itself to handle each inbound connection. Each connection is still handled using a separate process. The only difference is that the connection-handler process is now started by a master althttpd instance rather than by xinetd or stunnel4. Althttpd has no configuration file. All configuration is handled using a few command-line arguments. This helps to keep this configuration simple and mitigate worries about about introducing a security vulnerability through a misconfigured web server. Althttpd does not itself handle TLS connections. For HTTPS, althttpd relies on stunnel4 to handle TLS protocol negotiation, decryption, and encryption. Because each althttpd process only needs to service a single ................................................................................ The "-auth" file is plain text and line oriented. Blank lines and lines that begin with "#" are ignored. Other lines have meaning as follows: * <b>http-redirect</b> The http-redirect line, if present, causes all HTTP requests to redirect into an HTTPS request. * <b>https-only</b> The https-only line, if present, means that only HTTPS requests are allowed. Any HTTP request results in a 404 Not Found error. The https-only line normally occurs after an http-redirect line. |
|
|
|
>
>
|
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
...
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
|
itself listens on port 80 for incoming HTTP requests, then forks a copy of itself to handle each inbound connection. Each connection is still handled using a separate process. The only difference is that the connection-handler process is now started by a master althttpd instance rather than by xinetd or stunnel4. Althttpd has no configuration file. All configuration is handled using a few command-line arguments. This helps to keep the configuration simple and mitigates worries about about introducing a security vulnerability through a misconfigured web server. Althttpd does not itself handle TLS connections. For HTTPS, althttpd relies on stunnel4 to handle TLS protocol negotiation, decryption, and encryption. Because each althttpd process only needs to service a single ................................................................................ The "-auth" file is plain text and line oriented. Blank lines and lines that begin with "#" are ignored. Other lines have meaning as follows: * <b>http-redirect</b> The http-redirect line, if present, causes all HTTP requests to redirect into an HTTPS request. The "-auth" file is read and processes sequentially, so lines below the "http-redirect" line are never seen or processed for http requests. * <b>https-only</b> The https-only line, if present, means that only HTTPS requests are allowed. Any HTTP request results in a 404 Not Found error. The https-only line normally occurs after an http-redirect line. |