[
https://issues.apache.org/jira/browse/BROOKLYN-350?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15523193#comment-15523193
]
ASF GitHub Bot commented on BROOKLYN-350:
-----------------------------------------
Github user bostko commented on the issue:
https://github.com/apache/brooklyn-library/pull/64
@ygy Not very intuitive approach with using a ConfigKey. Still could be
sensible in some situations.
> Upstream yum repos for PostgresSQL started to enforce HTTPS
> -----------------------------------------------------------
>
> Key: BROOKLYN-350
> URL: https://issues.apache.org/jira/browse/BROOKLYN-350
> Project: Brooklyn
> Issue Type: Dependency upgrade
> Reporter: Yavor Yanchev
>
> The upstream YUM repos [1] provided by the PostgreSQL project started to
> enforce HTTPS.
> The PostgreSqlSshDriver uses curl to download RPMs from the upstream repo
> URL, but fails because it is redirected to the HTTPS location using a
> standard 301 header and curl is not instructed to follow the redirects.
> Example curl output
> {code}
> < HTTP/1.1 301 Moved Permanently
> < Location:
> https://yum.postgresql.org/9.4/redhat/rhel-6-x86_64/pgdg-centos94-9.4-2.noarch.rpm
> {code}
> If curl is instructed to follow the redirects with -L (--location) option the
> download will be successful
> [1] http://yum.postgresql.org
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
