From: Herve Rousseau <hroussea@cern.ch>
To: ceph-devel@vger.kernel.org
Subject: Re: [PATCH] Swift: Set Content-Length when requesting/checking Keystone tokens
Date: Mon, 27 Apr 2015 08:38:51 +0200 [thread overview]
Message-ID: <20150427063851.GA14185@adm01> (raw)
In-Reply-To: <1429979938-18465-1-git-send-email-hroussea@cern.ch>
On 25/04/15 18:38 +0200, Herve Rousseau wrote:
> From: Hervé Rousseau <hroussea@cern.ch>
>
> Running Keystone with WSGIChunkedRequest=On is not supported.
>
> We have to make sure that we set the Content-Length header when getting
> an admin token and checking revoked tokens, otherwise Keystone returns
> a HTTP 411 error.
>
> Same applies when checking revoked tickets.
>
> Signed-off-by: Hervé Rousseau <hroussea@cern.ch>
[snip]
Hi all,
We identified this issue when doing some integration tests with Keystone and
user/password authentication instead of using the admin token, it's related
to http://tracker.ceph.com/issues/7796.
We followed the aforementioned bug report and directives but then keystone
wouldn't work because they won't support Chunked encoding as their documentation
now reflects:
https://git.openstack.org/cgit/openstack/keystone/commit/?id=05c01e26d1e62298489ba3894576faf3c352e2c9
Cheers,
--
Hervé Rousseau
--
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
next prev parent reply other threads:[~2015-04-27 6:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-25 16:38 [PATCH] Swift: Set Content-Length when requesting/checking Keystone tokens Herve Rousseau
2015-04-27 6:38 ` Herve Rousseau [this message]
2015-04-27 15:35 ` Yehuda Sadeh-Weinraub
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=20150427063851.GA14185@adm01 \
--to=hroussea@cern.ch \
--cc=ceph-devel@vger.kernel.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.