From: nicolas.dely at technicolor.com (Nicolas Dely)
Subject: unexpected cache issue when http errors
Date: Mon, 30 Mar 2015 19:15:27 +0200 [thread overview]
Message-ID: <551984AF.6020203@technicolor.com> (raw)
Hi,
I would like to share an unexpected cache behaviour with this list and
discuss about a solution.
Indeed we are using cgit to provide a web interface to our internal user
and also to provide file to our reviewboard server.
We are experiencing some cache issue on static pages when data are not
pushed yet to server but reviewboard tries to access these
files/repositories. Cache is adding even 404, 401 or 500 error for
static page, we can workaround this issue after reducing/setting static
cache issue but it looks not very useful to cache http errors.
Do you think it is possible to only cache when HTTP is 200 OK? Other ideas?
PS: I've seen a cache issue (lock file) but nothing about http errors
Regards
Nicolas
next reply other threads:[~2015-03-30 17:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-30 17:15 nicolas.dely [this message]
2015-03-31 18:39 ` john
2015-04-01 14:25 ` nicolas.dely
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:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=551984AF.6020203@technicolor.com \
--to=cgit@lists.zx2c4.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 NNTP newsgroup(s).