From: Yehuda Sadeh-Weinraub <yehuda@redhat.com>
To: "Robin H. Johnson" <robbat2@gentoo.org>
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: Thu, 30 Jul 2015 14:26:15 -0400 (EDT) [thread overview]
Message-ID: <1563403567.1093721.1438280774967.JavaMail.zimbra@redhat.com> (raw)
In-Reply-To: <854662566.18884035.1435100864177.JavaMail.zimbra@redhat.com>
----- Original Message -----
> From: "Yehuda Sadeh-Weinraub" <yehuda@redhat.com>
> To: "Robin H. Johnson" <robbat2@gentoo.org>
> Cc: ceph-devel@vger.kernel.org, "Jonathan LaCour" <jonathan.lacour@dreamhost.com>
> Sent: Tuesday, June 23, 2015 4:07:44 PM
> Subject: Re: RGW S3 Website hosting, non-clean code for early review
>
>
>
> ----- Original Message -----
> > From: "Robin H. Johnson" <robbat2@gentoo.org>
> > To: "Yehuda Sadeh-Weinraub" <yehuda@redhat.com>
> > Cc: ceph-devel@vger.kernel.org, "Jonathan LaCour"
> > <jonathan.lacour@dreamhost.com>
> > Sent: Tuesday, June 23, 2015 4:04:49 PM
> > Subject: Re: RGW S3 Website hosting, non-clean code for early review
> >
> >
> > On Tue, Jun 23, 2015 at 04:30:19PM -0400, Yehuda Sadeh-Weinraub wrote:
> > > > Either I have to repeat a lot of code for it, which I'm not happy
> > > > about,
> > > > or I have to refactor RGWGetObj* to more safely made the second GET
> > > > request for the error object (and make sure range headers etc are NOT
> > > > used for the get of the error object). I'm leaning to the latter.
> > > Is generating a new req_state a possibility? E.g., you catch the error
> > > at the top level, and restart most of the request processing with a
> > > newly created req_state?
> > That was the path I was trying, but not completely succeeding.
> > I think need to step it back further and have a partially customized
> > copy of the RGWEnv from client_io->get_env(), so that I can build the
> > modified req_info for req_state.
> >
> > It isn't a full new GET really, it's really just custom content for the
> > body as well as some headers (mostly Content-Length, Content-Type), but
> > ignore EPERM/EACCESS on trying to fetch that custom content, and if they
> > are detected, consider that a success but with different HTML content.
> >
> > > Great! I'll wait for the cleaned up pull request.
> > Do you want pull requests per logical change of my proposed series
> > split, or rather just one pull request with the full series?
> >
>
> One pull request for the full series.
>
> Yehuda
> --
> To unsubscribe from this list: send the line "unsubscribe ceph-devel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
Hi,
just following up on this one. I don't remember seeing a pull request. Has there been any progress?
Thanks,
Yehuda
next prev parent reply other threads:[~2015-07-30 18:26 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 [this message]
2015-07-31 8:21 ` Robin H. Johnson
2015-12-02 14:02 ` Javier Muñoz
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=1563403567.1093721.1438280774967.JavaMail.zimbra@redhat.com \
--to=yehuda@redhat.com \
--cc=ceph-devel@vger.kernel.org \
--cc=jonathan.lacour@dreamhost.com \
--cc=robbat2@gentoo.org \
/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.