Cache default value is confusing

Hi, I think cache default value should be 0 by default, because 3600 seems like an arbitrary number.

Also, http-server seems a lot more suitable for development or testing purposes instead of production because of the lacking of pretty basic stuff, like routing.

What do you think?

[aletorrado]

Caching is usually an opt-in feature, because it may produce unexpected results.

El 14 ene. 2017 15:41, “Jannis Redmann” [e-mail] escribió:

Hi, I think cache default value should be 0 by default, because 3600 seems like an arbitrary number.

I disagree with 0 as it basically means no caching. 3600 at least seems to be the default of DNS A records. We might want to check the defaults of popular file servers.

Also, http-server seems a lot more suitable for development or testing purposes instead of production because of the lacking of pretty basic stuff, like routing.

I’d argue that routing is not a feature that a production-ready server must have.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/indexzero/http-server/issues/337#issuecomment-272643942, or mute the thread https://github.com/notifications/unsubscribe-auth/AARC_IxIaQF6sxcqc_6md5J3_ngtrVoKks5rSRbLgaJpZM4LjsaK .

[thornjad]

@aletorrado 3600 is not arbitrary, it’s one hour, which is a normal cache time for a static page. It’s also the default cache time in ecstatic, the core piece of http-server. It also makes sense when coupled with etags.

Closing due to inactivity, please reopen if this is still an issue.