infra-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Elek, Marton (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (INFRA-16717) Wrong SSL certificate for ozone.hadoop.apache.org
Date Wed, 05 Sep 2018 09:25:00 GMT

    [ https://issues.apache.org/jira/browse/INFRA-16717?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16604173#comment-16604173
] 

Elek, Marton commented on INFRA-16717:
--------------------------------------

I think it's a serious issue as the trend is to make harder and harder to check something
on http.

One workaround is using https://ozone.apache.org instead of https://ozone.hadoop.apache.org

Can we use 1st level subdomain for a subproject of a TLP?

/cc [~anu], [~arpiagariu], [~jnpandey]


> Wrong SSL certificate for ozone.hadoop.apache.org
> -------------------------------------------------
>
>                 Key: INFRA-16717
>                 URL: https://issues.apache.org/jira/browse/INFRA-16717
>             Project: Infrastructure
>          Issue Type: Planned Work
>          Components: Website
>            Reporter: Elek, Marton
>            Priority: Minor
>
> Thanks to the INFRA, ozone website is configured and available under http://ozone.hadoop.apache.org
(INFRA-16457)
> Unfortunately the https version of the same url doesn't work because the certificate
is valid only for  *.apache.org and apache.org. 
> Is it possible to add *.hadoop.apache.org to the valid domain names in the certificate?



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Mime
View raw message