You are viewing a plain text version of this content. The canonical link for it is here.
Posted to infrastructure-issues@apache.org by "jan iversen (JIRA)" <ji...@apache.org> on 2013/07/22 09:24:49 UTC
[jira] [Closed] (INFRA-6378) enable https://updates.openoffice.org
to use svn.
[ https://issues.apache.org/jira/browse/INFRA-6378?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
jan iversen closed INFRA-6378.
------------------------------
Resolution: Fixed
thx.
update works, cert implementation is not part of this jira.
> enable https://updates.openoffice.org to use svn.
> -------------------------------------------------
>
> Key: INFRA-6378
> URL: https://issues.apache.org/jira/browse/INFRA-6378
> Project: Infrastructure
> Issue Type: Wish
> Security Level: public(Regular issues)
> Components: Website
> Environment: ?
> Reporter: jan iversen
>
> http(s)://updates.openoffice.org and http(s)://ooo. updates.openoffice.org should use
> ^/openoffice/updates-site/trunk
> Svn is created, please do svnpubsub and other needed script to make it public.
> thx in advance
> comment from Oliver-Rainer Wittmann:
> damn - I just noticed that I have given the wrong fallback URL.
> It must be https://ooo-updates.apache.org/
> instead of https://ooo-updates.openoffice.org/
> Thus, we will not have a cert for openoffice.org in time for the AOO 4.0 release.
> Can we go for the _corrected_ fallback URL https://ooo-updates.apache.org for AOO 4.0 or do we have to keep https://ooo-site.apache.org?
> Both would be fine for me, but I heard that https://ooo-site.apache.org will not work for ever.
> comments from Rob Weir:
> Let's get a JIRA issue entered for creating that subdomain. I think
> Daniel suggested it that subdomain originally. That gives us the
> required SSL support for 4.0.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira