|
|
|
@ -1,4 +1,5 @@
|
|
|
|
|
- Not working behind Nginx (Works okay behind Caddy)
|
|
|
|
|
- Add byte counter in `trace!()` macro in the file server
|
|
|
|
|
- Not working great behind reverse proxies
|
|
|
|
|
- Show file server names in HTML
|
|
|
|
|
|
|
|
|
|
- Impl multi-range / multi-part byte serving
|
|
|
|
@ -58,3 +59,16 @@ I tried to figure out the percent encoding and it didn't work.
|
|
|
|
|
|
|
|
|
|
Maybe Base64 would be better or something? At least it's unambiguous and it
|
|
|
|
|
can go straight from UTF-8 to bytes to ASCII-armored.
|
|
|
|
|
|
|
|
|
|
## Turtle in Firefox's network debugger
|
|
|
|
|
|
|
|
|
|
The turtle shows up if Firefox has to wait more than 500 ms till first byte.
|
|
|
|
|
Curl says we can download a small file (950 bytes) end-to-end in about 250 ms.
|
|
|
|
|
|
|
|
|
|
So I think somewhere between Firefox and Caddy, something is getting confused.
|
|
|
|
|
Firefox, probably the same as Chromium, doesn't try to buffer entire videos
|
|
|
|
|
at once, so I think it purposely hangs the download, and then I'm not sure
|
|
|
|
|
what happens.
|
|
|
|
|
|
|
|
|
|
I might have to build a client that imitates this behavior, since it's hard
|
|
|
|
|
to control.
|
|
|
|
|