Don't Read My Blog

Solaris 11 Package Server Behind Apache Proxy

Solaris 11 Package Server Behind Apache Proxy

There is a great article about configuring multiple package internal package repositories here.  However, if you are looking to configure these behind an Apache proxy, you may have trouble.  I certainly did.

The issue boiled down to Apache not wanting to allow encoded slashes by default.  This resulted in Apache discarding the requests from pkg rather than passing them on to the pig-depot server.  The fix was to add AllowEncodedSlashes NoDecode to the httpd.conf file:

AllowEncodedSlashes NoDecode
SSLProxyEngine on
ProxyRequests Off
ProxyPreserveHost On
ProxyTimeout 30

ProxyPass /s11Repo11_1_20_5_0 http://localhost:10082 nocanon
ProxyPassReverse /s11Repo11_1_20_5_0 http://localhost:10082

2 thoughts on “Solaris 11 Package Server Behind Apache Proxy

    1. toddalancox Post author

      Thanks, I’ll check that out. With Solaris 11.0, we had originally just run with the pkg server directly. The original impetus of putting these behind Apache was to provide URLs which pointed to a specific version of the repository using snapshots. However, that was 4 years ago and we don’t publish multiple versions of the repo any more, though we do still take snapshots at each revision. We do use Apache as a reverse proxy on numerous services, and it’s continued to work well here.

      Thank you for the comment!

Leave a Reply

Your email address will not be published. Required fields are marked *