Interesting -- I don't see that behavior in curl, and we actually
do have the proper cert installed for patternfly:
SSL Server Certificate
Issued To
Common Name (CN) *.patternfly.org
Organization (O) Red Hat Inc.
Organizational Unit (OU) <Not Part Of Certificate>
Serial Number 02:51:C5:51:A1:11:D8:45:CA:B8:C1:FF:D8:3C:C2:D3
Maybe the cert isn't installed to all AWS locations properly? Very odd.
I'm in the eastern US.
Robb, looks like there is definitely some kind of
patternfly.org
misconfiguration happening.
Thanks for the help, Mirek!
Greg
----- Original Message -----
From: "Miroslav Suchy" <msuchy(a)redhat.com>
To: copr-devel(a)lists.fedorahosted.org
Sent: Thursday, January 29, 2015 10:43:35 AM
Subject: Re: help with failing build
On 01/29/2015 04:36 PM, Miroslav Suchy wrote:
> This is problem in mockchain:
I'm taking it back. This is completly correct.
curl
http://www.patternfly.org/wp-content/uploads/rpmsrc/patternfly1-1.1.3-1.f...
will print you redirect to https variant:
https://www.patternfly.org/wp-content/uploads/rpmsrc/patternfly1-1.1.3-1....
And the SSL certificate is issued only for '*.rhcloud.com',
'rhcloud.com' and therefore does not match
www.patternfly.org and python
library refuse to download it. Which is completely correct.
Either please remove the http->https redirect or create SSL certificate
which include
www.patternfly.org (you have to have silver+ plan in
OpenShift to do that) or just use different hosting (e.g.
people.fedorahosted.org)
Mirek
_______________________________________________
copr-devel mailing list
copr-devel(a)lists.fedorahosted.org
https://lists.fedorahosted.org/mailman/listinfo/copr-devel