Fossil SCM
Added section to the nginx-on-Debian server guide to cover client_max_body_size with `fossil uv sync`.
Commit
bd8d43767bf2a161b38a6ddb168fef9c667b31c8dee9684dba05c67f5b6c2630
Parent
53d3a755c1c6de2…
1 file changed
+16
| --- www/server/debian/nginx.md | ||
| +++ www/server/debian/nginx.md | ||
| @@ -217,10 +217,26 @@ | ||
| 217 | 217 | The most common thing people get wrong when hand-rolling a configuration |
| 218 | 218 | like this is to get the slashes wrong. Fossil is sensitive to this. For |
| 219 | 219 | instance, Fossil will not collapse double slashes down to a single |
| 220 | 220 | slash, as some other HTTP servers will. |
| 221 | 221 | |
| 222 | + | |
| 223 | +## <a name="large-uv"></a> Allowing Large Unversioned Files | |
| 224 | + | |
| 225 | +By default, nginx only accepts HTTP messages [up to a | |
| 226 | +meg](http://nginx.org/en/docs/http/ngx_http_core_module.html#client_max_body_size) | |
| 227 | +in size. Fossil chunks its sync protocol such that this is not normally | |
| 228 | +a problem, but when sending [unversioned content][uv], it uses a single | |
| 229 | +message for the entire file. Therefore, if you will be storing files | |
| 230 | +larger than this limit as unversioned content, you need to raise the | |
| 231 | +limit. Within the `location` block: | |
| 232 | + | |
| 233 | + # Allow large unversioned file uploads, such as PDFs | |
| 234 | + client_max_body_size 20M; | |
| 235 | + | |
| 236 | +[uv]: ../../unvers.wiki | |
| 237 | + | |
| 222 | 238 | |
| 223 | 239 | ## <a name="fail2ban"></a> Integrating `fail2ban` |
| 224 | 240 | |
| 225 | 241 | You can have `fail2ban` recognize attacks and automatically block them, |
| 226 | 242 | but the stock configuration doesn’t work with our Fossil setup above, so |
| 227 | 243 |
| --- www/server/debian/nginx.md | |
| +++ www/server/debian/nginx.md | |
| @@ -217,10 +217,26 @@ | |
| 217 | The most common thing people get wrong when hand-rolling a configuration |
| 218 | like this is to get the slashes wrong. Fossil is sensitive to this. For |
| 219 | instance, Fossil will not collapse double slashes down to a single |
| 220 | slash, as some other HTTP servers will. |
| 221 | |
| 222 | |
| 223 | ## <a name="fail2ban"></a> Integrating `fail2ban` |
| 224 | |
| 225 | You can have `fail2ban` recognize attacks and automatically block them, |
| 226 | but the stock configuration doesn’t work with our Fossil setup above, so |
| 227 |
| --- www/server/debian/nginx.md | |
| +++ www/server/debian/nginx.md | |
| @@ -217,10 +217,26 @@ | |
| 217 | The most common thing people get wrong when hand-rolling a configuration |
| 218 | like this is to get the slashes wrong. Fossil is sensitive to this. For |
| 219 | instance, Fossil will not collapse double slashes down to a single |
| 220 | slash, as some other HTTP servers will. |
| 221 | |
| 222 | |
| 223 | ## <a name="large-uv"></a> Allowing Large Unversioned Files |
| 224 | |
| 225 | By default, nginx only accepts HTTP messages [up to a |
| 226 | meg](http://nginx.org/en/docs/http/ngx_http_core_module.html#client_max_body_size) |
| 227 | in size. Fossil chunks its sync protocol such that this is not normally |
| 228 | a problem, but when sending [unversioned content][uv], it uses a single |
| 229 | message for the entire file. Therefore, if you will be storing files |
| 230 | larger than this limit as unversioned content, you need to raise the |
| 231 | limit. Within the `location` block: |
| 232 | |
| 233 | # Allow large unversioned file uploads, such as PDFs |
| 234 | client_max_body_size 20M; |
| 235 | |
| 236 | [uv]: ../../unvers.wiki |
| 237 | |
| 238 | |
| 239 | ## <a name="fail2ban"></a> Integrating `fail2ban` |
| 240 | |
| 241 | You can have `fail2ban` recognize attacks and automatically block them, |
| 242 | but the stock configuration doesn’t work with our Fossil setup above, so |
| 243 |