From: "Javier Muñoz" <jmunhoz@igalia.com>
To: "Robin H. Johnson" <robbat2@gentoo.org>,
Yehuda Sadeh-Weinraub <yehuda@redhat.com>
Cc: ceph-devel@vger.kernel.org,
Jonathan LaCour <jonathan.lacour@dreamhost.com>
Subject: Re: RGW S3 Website hosting, non-clean code for early review
Date: Wed, 02 Dec 2015 15:02:12 +0100 [thread overview]
Message-ID: <565EF9E4.2020501@igalia.com> (raw)
In-Reply-To: <robbat2-20150731T080643-628065411Z@orbis-terrarum.net>
Hi,
I would appreciate to know the current status of the implementation if
possible. Any progress? Any 'deadline' to go upstream? :)
Thanks in advance!
Javier
On 07/31/2015 10:21 AM, Robin H. Johnson wrote:
> I'm busy travelling and wrapping other things up, but will resume major
> work on this in August, probably week 2/3, depending on other
> interrupts/priorities.
>
> It's almost complete, the only missing features are:
> - error page fetcher gets confused on conditional requests (I think a
> different approach is needed, esp re range & if-modified requests,
> they still seem to leak into the custom req_info on the second request)
> - cascaded errors on conditional requests need more handling (eg
> 404 bounces to the error page that doesn't exist as well)
> Some further work that isn't blocking is also:
> - review handling of x-amz-website-redirect-location header when it
> conflicts with RoutingRules
> - Check what input validations Amazon does, because already they don't
> match the docs
> - eg docs say any http code for redirect, but it really only allows
> 301-305, 307, 308
> - Exact validation on the URI/paths is also not immediately clear, I
> had some unexpected results with URL-escaped inputs.
> - Review cases in which AMZ sets the errors in the header as well as the
> page, didn't seem consistent, esp in the double-error cases.
> - more cleanup/refactor of test cases
>
next prev parent reply other threads:[~2015-12-02 14:12 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-23 9:33 RGW S3 Website hosting, non-clean code for early review Robin H. Johnson
2015-06-23 20:30 ` Yehuda Sadeh-Weinraub
2015-06-23 23:04 ` Robin H. Johnson
2015-06-23 23:07 ` Yehuda Sadeh-Weinraub
2015-07-30 18:26 ` Yehuda Sadeh-Weinraub
2015-07-31 8:21 ` Robin H. Johnson
2015-12-02 14:02 ` Javier Muñoz [this message]
2015-12-03 21:47 ` Robin H. Johnson
2015-12-04 12:10 ` Javier Muñoz
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=565EF9E4.2020501@igalia.com \
--to=jmunhoz@igalia.com \
--cc=ceph-devel@vger.kernel.org \
--cc=jonathan.lacour@dreamhost.com \
--cc=robbat2@gentoo.org \
--cc=yehuda@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.