BlazeServe
A Python HTTP file server with byte ranges, cache headers, uploads, throttling, TLS, auth, and operational endpoints.
BlazeServe came from wanting something more serious than python -m http.server.
Quick file servers are useful until they need to behave like real software: large transfers, cache semantics, uploads, throttling, auth, and enough visibility to trust what is happening.
What It Does
BlazeServe is a Python HTTP file server with the details that usually get skipped:
- byte-range and multi-range responses
- ETag, Last-Modified, and If-Range handling
- zero-copy
sendfileandmmapfast paths - token-bucket rate limiting
- TLS, Basic Auth, CORS, uploads, and health/perf endpoints
The point was not to make a toy utility look serious. It was to make a small tool behave responsibly.
What Mattered
Simple tools are often simple because they ignore edge cases.
For BlazeServe, the edge cases were the project: cache headers, transfer paths, range requests, throttling, and authentication. Those details decide whether clients can trust the server under normal, imperfect conditions.
Why It Stayed
BlazeServe fits the work I like: protocol details, practical reliability, and software that still feels solid once it leaves the README.
It is a boring category taken seriously. That says a lot about how I prefer to build.