Question 1

Why does Static Web Server ignore my Cache-Control header for index.html files in subdirectories?

Accepted Answer

This is a known regression in version 2.40.1 where advanced header rules using glob patterns like '**/*.html' do not apply to directory index files (e.g., '/about/index.html' requested as '/about'). The bug is fixed in PR #613. Use the latest development Docker image (e.g., 'joseluisq/static-web-server:devel') or upgrade to a version that includes the fix once released.

Question 2

How to fix 'cp: unrecognized option: x' error when running the static-web-server installer on Alpine/BusyBox?

Accepted Answer

This error occurs because BusyBox's `cp` does not support the `-x` flag. It has been fixed in the installer script (PRs #610 and #611). Use the latest installer from https://get.static-web-server.net, which replaces `cp` with the `install` command and removes the sudo requirement. For Docker, rebuild the image without caching or pull the updated script. If you cannot upgrade immediately, manually copy the binary to the target path without the unsupported flag.

Question 3

How to fix RUSTSEC-2026-0009 denial of service via stack exhaustion in the Rust `time` crate?

Accepted Answer

Upgrade the `time` crate to version `0.3.47` or later, which adds a recursion-depth limit and returns an error instead of exhausting the stack. Run `cargo update -p time` and verify the resolved version with `cargo tree -i time`. Versions before `0.3.6` are unaffected. If upgrading is temporarily impossible, limit the length of user-supplied input passed to RFC 2822 parsing.

Question 4

Why does curl fail with "invalid block type" when sending Accept-Encoding: deflate with static-web-server compression-static enabled?

Accepted Answer

This is a content-negotiation bug in static-web-server v3.0.0-beta.1 and current `master` (`66b1288`). Both `gzip` and `deflate` were mapped to the `.gz` precompressed file, so a `deflate`-only request received gzip bytes with `Content-Encoding: deflate`, causing errors such as `invalid block type` or `incorrect header check`.

The fix maps only `ContentCoding::GZIP` to the `gz` extension. `deflate` has no static variant, so negotiation falls through to the next accepted coding, the identity file, or on-the-fly compression when enabled. Upgrade to a static-web-server release containing the PR "Serve the pre-compressed .gz variant only for gzip."

Temporary workarounds:

1. Request gzip instead of deflate-only:
```sh
curl --compressed -H 'Accept-Encoding: gzip' http://127.0.0.1:8787/
```

2. Or disable precompressed static files in the configuration:
```toml
[general]
compression-static = false
```

Verify the response with:
```sh
curl -sS -D - -o body.bin -H 'Accept-Encoding: deflate' http://127.0.0.1:8787/
head -c 4 body.bin | xxd
```
A gzip body starts with `1f8b`, but it must not be returned with `Content-Encoding: deflate`.

static-web-server

Core Features

What It Can't Do

Use Cases

Tags

Getting Started

Similar Projects