- From: Jonathan Matthews <
>
- To:
- Subject: [chef] Re: How to Proxy Chef Server with Apache, simpler setup...
- Date: Fri, 2 Jul 2010 10:26:19 +0100
On 28 June 2010 18:53, Miguel Cabeça
<
>
wrote:
>
Hi all,
>
>
I have a somewhat simpler apache setup than the one featured on the Wiki.
>
It has the advantage of requiring only the default https port for both API
>
and WebUI access.
>
mod_rewrite points to the right merb instance based on the existence of the
>
X-Chef-Version header presented by API clients.
I like this approach, but I wonder if the API genuinely insists on
X-Chef-Version and rejects requests from, say, badly-written clients -
despite the header being documented as required. Perhaps it might be
more predictable to rely on a header that's absolutely essential to
API access: one of those in mixlib/authentication/signedheaderauth.rb:
X-Ops-Sign, X-Ops-Userid, X-Ops-Timestamp or X-Ops-Content-Hash?
Regards,
Jonathan
--
Jonathan Matthews
London, UK
http://www.jpluscplusm.com/contact.html
- [chef] Re: How to Proxy Chef Server with Apache, simpler setup..., Jonathan Matthews, 07/02/2010
Archive powered by MHonArc 2.6.16.