[chef] Re: Authentication errors for requests through Apache HTTPS proxy

[Vladimir Girnet < >]

I see a bit different rewrite rule in my configuration, may be this is the 
cause?

RewriteRule ^/(.*)$ http://127.0.0.1:4000%{REQUEST_URI} [P,QSA,L]


On May 15, 2012, at 11:52 AM, Janne Liuhtonen wrote:

> Hi,
> 
> I'm trying to proxy the connection to chef-server with Apache and
> mod_proxy. The proxy seems to work, I get the Chef server API front
> page displayed correctly and for example "knife client list" works.
> Uploading new data or updating existing data however doesn't work and
> I'm 403 errors. Example:
> 
> 
> 
> Apache configuration:
> 
> <VirtualHost *:443>
>  ServerName my.chef.server.com
> 
>  DocumentRoot /usr/lib64/ruby/gems/1.8/gems/chef-server-api-0.10.8/public
> 
>  SSLEngine on
>  SSLCertificateFile /etc/certs/chef/chef-server.crt
>  SSLCertificateKeyFile /etc/certs/chef/chef-server.key
>  RequestHeader set X_FORWARDED_PROTO 'https'
> 
>  AllowEncodedSlashes   on
> 
>  RewriteEngine on
>  RewriteCond %{DOCUMENT_ROOT}/%{REQUEST_FILENAME} !-f
>  RewriteRule ^/(.*)$ http://127.0.0.1:4000/$1 [P]
> 
>  ErrorLog logs/chef_error_log
>  TransferLog logs/chef_access_log
>  LogLevel info
> 
> </VirtualHost>
> 
> Using chef server with port 4000 directly works without any problems.
> 
> Any clues what might cause this?

--
Vladimir Girnet
Infrastructure Engineer
Tacit Knowledge
http://www.tacitknowledge.com