Fossil SCM
Added a similar message to the OpenBSD httpd guide as in [bd8d4376].
Commit
7252f7a40a7d21489437c600b60e68a6893c9789e1fe547d6212f3633e3892c1
Parent
162b7abbe067ca0…
1 file changed
+12
| --- www/server/openbsd/fastcgi.md | ||
| +++ www/server/openbsd/fastcgi.md | ||
| @@ -159,15 +159,27 @@ | ||
| 159 | 159 | root "/acme" |
| 160 | 160 | request strip 2 |
| 161 | 161 | } |
| 162 | 162 | } |
| 163 | 163 | ``` |
| 164 | + | |
| 165 | +[The default limit][dlim] for HTTP messages in OpenBSD’s `httpd` server | |
| 166 | +is 1 MiB. Fossil chunks its sync protocol such that this is not | |
| 167 | +normally a problem, but when sending [unversioned content][uv], it uses | |
| 168 | +a single message for the entire file. Therefore, if you will be storing | |
| 169 | +files larger than this limit as unversioned content, you need to raise | |
| 170 | +the limit as we’ve done above with the “`connection max request body`” | |
| 171 | +setting, raising the limit to 100 MiB. | |
| 172 | + | |
| 173 | +[dlim]: https://man.openbsd.org/httpd.conf.5#connection | |
| 174 | +[uv]: ../../unvers.wiki | |
| 164 | 175 | |
| 165 | 176 | **NOTE:** If not already in possession of a HTTPS certificate, comment |
| 166 | 177 | out the `https` server block and proceed to securing a free |
| 167 | 178 | [Let's Encrypt Certificate](#letsencrypt); otherwise skip to |
| 168 | 179 | [Start `httpd`](#starthttpd). |
| 180 | + | |
| 169 | 181 | |
| 170 | 182 | ## <a name="letsencrypt"></a>Let's Encrypt Certificate |
| 171 | 183 | |
| 172 | 184 | In order for `httpd` to serve HTTPS, secure a free certificate from |
| 173 | 185 | Let's Encrypt using `acme-client`. Before issuing the request, however, |
| 174 | 186 |
| --- www/server/openbsd/fastcgi.md | |
| +++ www/server/openbsd/fastcgi.md | |
| @@ -159,15 +159,27 @@ | |
| 159 | root "/acme" |
| 160 | request strip 2 |
| 161 | } |
| 162 | } |
| 163 | ``` |
| 164 | |
| 165 | **NOTE:** If not already in possession of a HTTPS certificate, comment |
| 166 | out the `https` server block and proceed to securing a free |
| 167 | [Let's Encrypt Certificate](#letsencrypt); otherwise skip to |
| 168 | [Start `httpd`](#starthttpd). |
| 169 | |
| 170 | ## <a name="letsencrypt"></a>Let's Encrypt Certificate |
| 171 | |
| 172 | In order for `httpd` to serve HTTPS, secure a free certificate from |
| 173 | Let's Encrypt using `acme-client`. Before issuing the request, however, |
| 174 |
| --- www/server/openbsd/fastcgi.md | |
| +++ www/server/openbsd/fastcgi.md | |
| @@ -159,15 +159,27 @@ | |
| 159 | root "/acme" |
| 160 | request strip 2 |
| 161 | } |
| 162 | } |
| 163 | ``` |
| 164 | |
| 165 | [The default limit][dlim] for HTTP messages in OpenBSD’s `httpd` server |
| 166 | is 1 MiB. Fossil chunks its sync protocol such that this is not |
| 167 | normally a problem, but when sending [unversioned content][uv], it uses |
| 168 | a single message for the entire file. Therefore, if you will be storing |
| 169 | files larger than this limit as unversioned content, you need to raise |
| 170 | the limit as we’ve done above with the “`connection max request body`” |
| 171 | setting, raising the limit to 100 MiB. |
| 172 | |
| 173 | [dlim]: https://man.openbsd.org/httpd.conf.5#connection |
| 174 | [uv]: ../../unvers.wiki |
| 175 | |
| 176 | **NOTE:** If not already in possession of a HTTPS certificate, comment |
| 177 | out the `https` server block and proceed to securing a free |
| 178 | [Let's Encrypt Certificate](#letsencrypt); otherwise skip to |
| 179 | [Start `httpd`](#starthttpd). |
| 180 | |
| 181 | |
| 182 | ## <a name="letsencrypt"></a>Let's Encrypt Certificate |
| 183 | |
| 184 | In order for `httpd` to serve HTTPS, secure a free certificate from |
| 185 | Let's Encrypt using `acme-client`. Before issuing the request, however, |
| 186 |