One more thing: Artifactory recommends setting the header RequestHeader set X-Artifactory-Override-Base-Url "http://artifactory.organization.com:8081/artifactory";
I do not: If you add the header, the Docker client will try to connect directly to the Artifactory server at port 8081. This causes two problems: The traffic is unencrypted, and you need to open port 8081 in the firewall. If you omit the header, all traffic is forced through the proxy at the SSL port. This gives better security and a port less to administrate in the firewall setup. The hack was needed with Artifactory 4.4.0, but it appears to work without it again in 4.4.2. Regards, Lars -- View this message in context: http://forums.jfrog.org/Docker-broken-again-in-4-4-0-tp7580708p7580803.html Sent from the Artifactory - Users mailing list archive at Nabble.com. ------------------------------------------------------------------------------ Site24x7 APM Insight: Get Deep Visibility into Application Performance APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month Monitor end-to-end web transactions and take corrective actions now Troubleshoot faster and improve end-user experience. Signup Now! http://pubads.g.doubleclick.net/gampad/clk?id=272487151&iu=/4140 _______________________________________________ Artifactory-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/artifactory-users
