which causes a 404 on the client end.
Note that the downloads_path is absolute (e.g. here it is usually /workspace/downloads/5001/test.mp4), not relative to the current directory. Is that an issue?
Any ideas?
I'd assume it tries to serve /workspace/downloads/5001/test.mp4 from your computer. If you want to serve $PWD/workspace/downloads/5001/test.mp4, I'd remove the leading slash and try again.
on their machine, and place a file that is then requested in /workspace/downloads/5001.
I just tested just that on my device and still get a 404 not found.
I'm very confused why this isn't working.
Any help would be appreciated!
I think the problem is the warp::path! macro. Especially this section seems relevant, though I don't know what end() does in warp-land. But if I change your route to this:
let route = warp::path!("api" / "persistent-videos" / ..).and(warp::fs::dir("/tmp"));
or
let route = warp::path("api")
.and(warp::path("persistent-videos"))
.and(warp::fs::dir("/tmp"));