Notes |
|
(0020739)
|
HiM
|
2019-06-10 20:13
|
|
|
|
|
|
|
(0020741)
|
HiM
|
2019-06-10 20:52
|
|
Hmm, but it was not working until readded in 1.2 Doomseeker.
Maybe HTTP vs HTTPS is a cause? In Bitbucket is HTTPS.
Shouldnt it be coded as "http://static.allfearthesentinel.net/wads/" ? |
|
|
(0020742)
|
Pol M
|
2019-06-10 22:21
|
|
Tested in a clean config, the default link works properly and can download wads. Https should always be preferred since it adds a layer of encryption that is always appreciated (you know, last thing we want is a man in the middle ;) ). Could you describe a reproducible environment where https does not work? If you test it on a clean config and it works, then this ticket may be set as resolved. |
|
|
|
I believe this works as intended. |
|
|
|
Specifically, I don't think we do config migrations from 1.0 to 1.2 with Wadseeker sites. But the site is there, since 1.1.
If this is an issue, report a new issue. |
|
|
|
Quote from WubTheCaptain If this is an issue, report a new issue.
...now 0003661. |
|
|
|
(Setting this issue's status back to invalid, since OP reported the issue in Doomseeker 1.2 originally. I'll keep the duplicate tracker.) |
|
|
(0020757)
|
Zalewa
|
2019-06-13 14:56
|
|
There's a "Always use Wadseeker's default sites" checkbox in the "Wadseeker/Sites" config page. If it's checked, Wadseeker will always use the up-to-date hardcoded sites, no matter what's on the list in the config page. If the checkbox is unchecked, only the sites listed on the page are used. |
|