I need it because I have frontend apache proxy that is used by many
different clients including chef-client.
I have configured the proxy to to forward requests https://myproxy/chef-server-api to http://mychefserver:4000/
but it does not work as the mixlib-authentication library used by
chef-client use URI PATH for creating signature
and because the leading part of the URI PATH for the original request
was cut off by the proxy, the chef-server receives different
URI PATH, calculate a non matched signature and authentication of the
request fails.
I think that It should be possible via some merb route configuration but
do’nt know how do do
ATTENTION:
The information in this electronic mail message is private and
confidential, and only intended for the addresses. Should you
receive this message by mistake, you are hereby notified that
any disclosure, reproduction, distribution or use of this
message is strictly prohibited. Please inform the sender by
reply transmission and delete the message without copying or
opening it.
I need it because I have frontend apache proxy that is used by
many different clients including chef-client.
I have configured the proxy to to forward requests https://myproxy/chef-server-api to http://mychefserver:4000/
but it does not work as the mixlib-authentication library used by
chef-client use URI PATH for creating signature
and because the leading part of the URI PATH for the original request was
cut off by the proxy, the chef-server receives different
URI PATH, calculate a non matched signature and authentication of the
request fails.