yhirose
bef278e0d2
Samples that did not compile or run as shown: - res.user_data.get<T>() inside a generic lambda needs the `template` keyword; use explicit parameter types (tour 09, cookbook s15). - listen() on a Unix domain socket fails with port 0 (tour 09, s22). - "*.dev.local" is not a NO_PROXY pattern (c16). - ssl_backend_error() holds a verify result, not an ERR_get_error() value, after a verification failure; decode each with the matching OpenSSL function (c18). - The content provider's `length` is everything that remains, so the sample read the whole file in one call (s05). Statements corrected: - Client keep-alive is off by default; c14 is rewritten around set_keep_alive(true). - Mounted files are looked up before GET handlers (tour 04, s04). - Params keep insertion order, and to_string(Error::Connection) reads "Could not establish connection" (tour 02). - A chunked provider ends with sink.done(), and post_routing_handler runs before the response is sent (tour 09). - Timeouts surface as Error::Read; Error::Timeout comes from the stream API (c17). The max timeout cuts off the wait for the response only (c13). The progress callback needs Content-Length (c11). - Encoding selection follows q-values, then Brotli, gzip, Zstd (s08), and the client compresses with the first of those it was built with (c15). - stop() cuts a provider-driven response short (s19); a rejected content_reader already gets 400 or 413 (s07); user_data values must be copyable (s12); Client accepts a client certificate too (t04); on_message() is the fallback for every unhandled event and 204/403/404 end reconnection (e04); the pong timeout takes two to three intervals and ends a waiting read() (w02). In the LLM app tutorial, an uncaught exception does not crash the server, so say what it does instead. Drop the server and client timeout settings whose stated purpose, covering inference and download time, they do not serve: those timeouts bound a single socket wait. Update the llama.cpp server layout in chapter 7.
1.8 KiB
title, order, status
| title | order | status |
|---|---|---|
| S04. Serve Static Files | 23 | draft |
To serve static files like HTML, CSS, and images, use set_mount_point(). Just map a URL path to a local directory, and the whole directory becomes accessible.
Basic usage
httplib::Server svr;
svr.set_mount_point("/", "./public");
svr.listen("0.0.0.0", 8080);
./public/index.html is now reachable at http://localhost:8080/index.html, and ./public/css/style.css at http://localhost:8080/css/style.css. The directory layout maps directly to URLs.
Multiple mount points
You can register more than one mount point.
svr.set_mount_point("/", "./public");
svr.set_mount_point("/assets", "./dist/assets");
svr.set_mount_point("/uploads", "./var/uploads");
You can even mount multiple directories at the same path — they're searched in registration order, and the first hit wins.
Combine with API handlers
Static files and API handlers coexist happily. For GET and HEAD, the mount points are searched first; handlers registered with Get() and friends run only when no file is found.
svr.Get("/api/users", [](const auto &req, auto &res) {
res.set_content("[]", "application/json");
});
svr.set_mount_point("/", "./public");
This gives you an SPA-friendly setup: /api/* hits the handlers, everything else is served from ./public/.
Add MIME types
cpp-httplib ships with a built-in extension-to-Content-Type map, but you can add your own.
svr.set_file_extension_and_mimetype_mapping("wasm", "application/wasm");
Warning: The static file server methods are not thread-safe. Don't call them after
listen()— configure everything before starting the server.
For download-style responses, see S06. Return a file download response.