| Additional Information | > For the class of issues "HTTPS supported but not listed":
> ATM the list is maintained manually, so if changes are not
> notified, they are not reflected. The list was updated with this
> class of issues unless I missed some.
For things like this I'll be saying "https: [N/A]", which will mean the
mirror list says it's not supported. So just as this email prompted
some mirror admins to say "hey, we do support HTTPS now", this should
prompt similar reports, and thus we can manually update the list.
Maybe I could test HTTPS anyway, then report "https: [OK, fix list]" or
some such.
...
> > The official mirror list says "temporarily-offline", so my
> > mirror
> > checker doesn't bother to check it. I should probably add an
> > option to
> > check it anyway, so the admin of this mirror knows what works
> > and what
> > doesn't.
>
> It was removed of the RR because it was being problematic; we
> never got an answer so I just changed the state to "offline".
That's an argument for "test it anyway". If it starts showing
consistently good results, we could change it back to "Active: yes".
Though feedback to "Are you having problems" questions is also good.
|
|---|
related to 
child of 
duplicate of 
