rack-devel archive mirror (unofficial) https://groups.google.com/group/rack-devel
 help / color / mirror / Atom feed
From: Magnus Holm <judofyr@gmail.com>
To: rack-devel@googlegroups.com
Subject: Re: Middleware for serving static files
Date: Tue, 20 Dec 2011 09:45:53 +0100	[thread overview]
Message-ID: <CAJ367fdE16QQ=YkWTEpy5PJFyiBoq7Vn2Vivz515hnr52SBxtw@mail.gmail.com> (raw)
In-Reply-To: <ACA1B811C0CE46CDA19BB8F3E5C7D26E@gmail.com>

On Tue, Dec 20, 2011 at 09:41, Lee Hambley <lee.hambley@gmail.com> wrote:
> Make your own middleware that detects a URI if `/style.css`, and respond
> with `/files/style.css` using Rack::Static?

Meh, the Before-solution is better then. It isn't hard to solve the
problem, I'm just wondering why Rack doesn't give us a way to do it
out-of-box. It seems like a pretty basic functionality…

  reply	other threads:[~2011-12-20  8:46 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-20  8:32 Middleware for serving static files Magnus Holm
2011-12-20  8:41 ` Lee Hambley
2011-12-20  8:45   ` Magnus Holm [this message]
2011-12-20  8:52     ` Lee Hambley
2011-12-20  9:07       ` Magnus Holm
2011-12-21  2:49         ` James Tucker

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='CAJ367fdE16QQ=YkWTEpy5PJFyiBoq7Vn2Vivz515hnr52SBxtw@mail.gmail.com' \
    --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).