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]). Using .htacess is not going to
give us the best performance, though.
So, AFAIK, the plan is (correct me if wrong)
1. Redirect netbeans.org to netbeans.apache.org
Already done at https://issues.apache.org/jira/browse/INFRA-17245
Note that only the netbeans.org (and www.netbeans.org) CNAMES will be
redirected.
The rest (wiki.netbeans.org, platform.netbeans.org, hg.netbeans.org,
etc., should not be altered). platform.netbeans.org could be also
redirected, I think.
2. See if anything breaks.
3. Do incremental upgrades to HTTPS (as in [1] below)
4. See if anything breaks.
5. goto 3 until everything works.
6. Remove incremental HTTPS upgrades in .htaccess
7. Done.
Cheers,
Antonio
[1]
https://www.inmotionhosting.com/support/website/ssl/how-to-force-https-using-the-htaccess-file/
El 15/3/20 a las 11:56, Neil C Smith escribió:
On Sun, 15 Mar 2020, 10:24 antonio, <[email protected]> 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. before
that. Possibly anything html?
Best wishes,
Neil
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
