unicorn Ruby/Rack server user+dev discussion/patches/pulls/bugs/help
 help / color / mirror / code / Atom feed
From: Xavier Noria <fxn@hashref.com>
To: unicorn-public <unicorn-public@bogomips.org>
Subject: Re: No, passenger 5.0 is not faster than unicorn :)
Date: Wed, 3 Dec 2014 13:42:16 +0100	[thread overview]
Message-ID: <CAM=YcdgW34s0aZp9QaPRW8cdu57acSvkuL+K94Mh250Of=CaRQ@mail.gmail.com> (raw)
In-Reply-To: <CAAtdryPyLu0LBk9Gh_O3it-BXq_A_B-RnftRmVM=SKB7AcydCQ@mail.gmail.com>

I've often found Cache-Control: public to be of limited use in practice
because you cannot invalidate that cache by hand. (Sometimes that's fine of

While the reverse proxy cache could provide a mechanism for explicit
expiration, there may be caches between your servers and the client, a
corporate cache for example. Those other ones are out of your control.

I suggested an extension for Rack::Cache called r-maxage that got merged:


With that directive you trade the benefits of caching in intermediate
proxies with more expiration control locally.

  reply	other threads:[~2014-12-03 12:42 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-03  9:50 No, passenger 5.0 is not faster than unicorn :) Bráulio Bhavamitra
2014-12-03  9:56 ` Sam Saffron
2014-12-03  9:57   ` Sam Saffron
2014-12-03 11:00 ` Hongli Lai
2014-12-03 11:05   ` Sam Saffron
2014-12-03 12:42     ` Xavier Noria [this message]
2014-12-03 14:10   ` Bráulio Bhavamitra

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-all from there: mbox

  Avoid top-posting and favor interleaved quoting:

  List information: https://yhbt.net/unicorn/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAM=YcdgW34s0aZp9QaPRW8cdu57acSvkuL+K94Mh250Of=CaRQ@mail.gmail.com' \
    --to=fxn@hashref.com \
    --cc=unicorn-public@bogomips.org \


* 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.
Code repositories for project(s) associated with this public inbox


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).