If someone has a setup where https does not work, the consequences will be worse in 3.0.3 than they've been with earlier releases, as we now have the default metaserver URL and modpack list URL defined to use https. To prevent such a regression (-> reason to stick with earlier, otherwise more buggy, freeciv-3.0 releases) I'd suggest that we still support (though won't recommend) defining those default URLs to use http. That can be made by adding a new .project file with URLs of its own.
This is strictly for S3_0 only. For freeciv-3.1 series one is expected to have https support. There's no "regression" within the freeciv-3.1 series (when updating from one freeciv-3.1 release to another) as the situation is that from the beginning.
If someone has a setup where https does not work, the consequences will be worse in 3.0.3 than they've been with earlier releases, as we now have the default metaserver URL and modpack list URL defined to use https. To prevent such a regression (-> reason to stick with earlier, otherwise more buggy, freeciv-3.0 releases) I'd suggest that we still support (though won't recommend) defining those default URLs to use http. That can be made by adding a new .project file with URLs of its own.
This is strictly for S3_0 only. For freeciv-3.1 series one is expected to have https support. There's no "regression" within the freeciv-3.1 series (when updating from one freeciv-3.1 release to another) as the situation is that from the beginning.