It also doesn't cache in memory by default (but I'm considering to change
that).
As for custom 404 handlers, I think that's a great idea. I'll work on it
tomorrow, thanks.
On Saturday, August 4, 2012 10:14:02 AM UTC-5, Felix E. Klee wrote:
I'm testing Lactate now.
Questions and remarks:
* How do I disable client (browser) side caching?
Without the `expires` option being set, just no `Cache-Control`
header is returned. Is that enough? In general I though that
something as the following is required:
Cache-Control:max-age=0, no-cache
* Although I said earlier that I don't need it, I now think it would
be a nice idea to emit a custom 404 page for invalid paths (I check
that myself). So it would be nice if I could serve a file with 404
status code.
Custom headers may be a great addition!
--I'm testing Lactate now.
Questions and remarks:
* How do I disable client (browser) side caching?
Without the `expires` option being set, just no `Cache-Control`
header is returned. Is that enough? In general I though that
something as the following is required:
Cache-Control:max-age=0, no-cache
* Although I said earlier that I don't need it, I now think it would
be a nice idea to emit a custom 404 page for invalid paths (I check
that myself). So it would be nice if I could serve a file with 404
status code.
Custom headers may be a great addition!
Job Board: http://jobs.nodejs.org/
Posting guidelines: https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines
You received this message because you are subscribed to the Google
Groups "nodejs" group.
To post to this group, send email to nodejs@googlegroups.com
To unsubscribe from this group, send email to
nodejs+unsubscribe@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/nodejs?hl=en?hl=en
