On 12/07/11 22:46, Lyle T. Harris wrote:
On 12/7/11 5:07 PM, Shawn Walker wrote:
The depot server itself is run via HTTP and then reverse-proxied to
Apache which serves requests via SSL.
Therefore caching is possible.
The SRU depot server itself is running https
No, it is not.
The depot server is running http on a private port that is not
accessible to the outside world, which is then reverse-proxied by Apache
over https.
So when a client connects to the repository it does so through the
Apache cache over SSL.
(https://pkg.oracle.com/solaris/support)
so not sure how any proxy between that and the client is going to
provide caching..
A certificate is required for SRU access.
Found this regarding https and caching for reference:
http://www-uxsup.csx.cam.ac.uk/~jw35/courses/using_https/html/x183.htm
You're misunderstanding what I was suggesting to improve performance.
My suggestion for improving performance using cache applies only to the
server where the package data is being served from.
On a corporate network, the best performance can be achieved by setting
up a private depot server using the repository ISO images we provide and
then using Apache in a reverse-proxy setup with caching to provide
access to the repository for clients.
-Shawn
_______________________________________________
caiman-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/caiman-discuss
