serveStatic should allow omission of max-age from Cache-Control? about plugins HOT 1 CLOSED

Hey @zyrolasting,

Thank you for opening this issue! We know serveStatic has quite a few short-comings. In fact, its almost easier at this point to just wire the fs module directly up to restify as opposed to trying to use this middleware. To answer your question, your approach looks pretty sane from a high level.

serveStatic has been a point of contention for a while. Dicussion is fragmented across a few different issues over at https://github.com/restify/node-restify

I believe the current plan is to eventually move serveStatic out into it's own module outside of the restify repo. The thought process is that restify is designed for building semantically correct, production ready, REST services designed for scale. Serving static content is outside of that wheelhouse. In addition, Node.js isn't the best at serving static content, you often get better mileage by fronting your restify service with NGinx for that use case. We know a lot of people are building webapps with restify, and that serving static content directly from Node.js simplifies that use case, so we are going to try to do this with care. If you would be interested in helping with that effort, or just want to chime in on the discussion, let us know ❤️

In the meantime, we are merging the plugins back into the core restify repo. Feel free to open an issue over there if you still have questions and I would be happy to help 😄

from plugins.