iron / iron/staticfile

Support client caching

Open
#97 3 comments 1 reaction 0 assignees View on GitHub
Dominant language
Rust
Stars
66
Forks
57
PR merge metrics
No merged PRs in 30d

Description

I'm trying to serve assets using this crate, but I've noticed the server does not send an Etag. This would cause the client to request the asset every time it's referenced (so, on every page load).

The express framework is sending an etag on static mounts, the client would memorize this and include it in future requests, if the server notices the file hasn't changed, it's sending back an 304.

This is critical for page speed and bandwidth. :)

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.