From: Eric Wong <normalperson@yhbt.net>
To: rack-devel@googlegroups.com
Subject: Re: Patch - For caching with 304 Not Modified
Date: Wed, 21 Jul 2010 18:16:34 +0000 [thread overview]
Message-ID: <20100721181634.GA7794@dcvr.yhbt.net> (raw)
In-Reply-To: <39c82ee3-5030-4721-9be8-0b1927dce3f1@x21g2000yqa.googlegroups.com>
Simon Smith <amazingdancingbear@gmail.com> wrote:
> This patch seems to work but it seems strange that it is missing in
> the first place as there are so many users of Rack and Rails and I
> cannot find any information pertaining to other users with this
> problem. I am wondering if there is an alternate way to handle this
> caching without modifying the rack code itself and I am just missing a
> configuration option in Rails, do you know of one?
Rack already includes a Rack::ConditionalGet middleware which users can
load if needed.
However, I suspect most Rails users use a non-Rack server such as nginx
or Apache to serve static files, so having such middleware (or even
Rack::File) would be redundant.
--
Eric Wong
next prev parent reply other threads:[~2010-07-21 18:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-21 15:23 Patch - For caching with 304 Not Modified Simon Smith
2010-07-21 18:16 ` Eric Wong [this message]
2010-07-21 18:59 ` Simon Smith
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-list from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://groups.google.com/group/rack-devel
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20100721181634.GA7794@dcvr.yhbt.net \
--to=rack-devel@googlegroups.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).