Let's go then.
Do we want to also redirect wiki.netbeans.org to
netbeans.apache.org/wiki and platform.netbeans.org/tutorials to
netbeans.apache.org/tutorials or do we want to do that later on?
Thanks,
Antonio
El 15/3/20 a las 19:08, Geertjan Wielenga escribió:
Let’s do that, i.e., have infr
Let’s do that, i.e., have infra do it, and iterate as needed.
Gj
On Sun, 15 Mar 2020 at 19:03, antonio wrote:
> Hi,
>
> netbeans.apache.org infrastructure is _not_ under our control, it's ASF
> Infra that's handling the infrastructure. So we cannot modify the web
> server settings, for example.
Hi,
netbeans.apache.org infrastructure is _not_ under our control, it's ASF
Infra that's handling the infrastructure. So we cannot modify the web
server settings, for example.
All we can do is to modify the .htaccess and do incremental upgrades to
HTTPS for certain sections (as in [1]). Usin
Let’s do the incremental approach — and we can do all this on the Apache
side, without Infra involvement, right? If so, shall we start with the home
page and see how it goes?
Gj
On Sun, 15 Mar 2020 at 11:56, Neil C Smith wrote:
> On Sun, 15 Mar 2020, 10:24 antonio, wrote:
>
> > Once we check 1
On Sun, 15 Mar 2020, 10:24 antonio, wrote:
> Once we check 1. works we can proceed with 3, and see if all tooling is
> able to dowload DTDs using HTTPS.
>
That assumes blanket https redirect. We could do this incrementally,
redirect key pages to https, eg. home page, downloads section, etc. befo
Hi,
I've just seen this message.
The suggested order is to follow baby steps in this order:
1. Reroute netbeans.org to netbeans.apache.org.
2. See if anything breaks.
3. Enforce https on the site.
4. See if anything breaks.
We tried 1. above a while back, and we discovered that the build syste
