| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
| |
Many of these fall into a few categories:
- util.cache size, must be >= 1
- byte or item counts that logically can't be negative
- port numbers that should be in 1..0xffff
|
| |
|
|
|
|
|
|
|
|
|
| |
It is time. Most community modules should have been adjusted to work
with the new (net.http.files) way.
At some point this usage should be prevented.
Related to #1765
|
|
|
|
|
|
| |
Words, sometimes I wonder how they even work
Maybe I missed something.
|
|
|
|
|
| |
Not that much to worry about, the most common file types are included in
the code above.
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
deal with it
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
| |
RFC 2616 section 14 (header field definitions) shows that ETag header content
should be wrapped in double quotes.
|
|\ |
|
| | |
|
| | |
|
| | |
|
|\| |
|
| |
| |
| |
| | |
it to a filesystem path, fixes a relative path traversal vulnerability
|
|\| |
|
| | |
|
| |
| |
| |
| | |
directionality of the slash (fixes #545)
|
|\| |
|
| |
| |
| |
| | |
Windows (thanks Junne)
|
|/ |
|
|
|
|
| |
per-host
|
| |
|
| |
|
|
|
|
| |
routes with file paths to serve
|
|
|
|
| |
HTTP path.
|
|
|
|
| |
plugin to generate it
|
|
|
|
| |
Don't serve files by default unless http_files_dir is set
|
| |
|
| |
|
| |
|
|
|
|
| |
present
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
/etc/mime.types if exists.
|
| |
|
| |
|