This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
as suggested by karen
Setting severity to enhancement and reassigning. The link checker code itself is fully ready for HTTPS (just verified on my dev box), but the public service doesn't support it due to missing libraries, I guess. See <http://search.cpan.org/dist/libwww-perl/README.SSL> for more info. Olivier, could the required SSL libs be installed to v.w.o?
libcrypt-ssleay-perl installed. Ville, tell me if you need anything else for SSL support.
Validation looks good, but please also provide the icons under https such that security aware browsers don't complain (http://www.w3.org/Bugs/Public/show_bug.cgi?id=117)
The whole Validator interface, not only the icons, needs to be available thru HTTPS. Otherwise the "referer" URLs will break for people who are using a well behaving browser. See bug 77 for more discussion about this. Please post comments to the relevant bugs instead of opening old ones, this was already resolved; checklink now does https: URLs. Thanks. Oh, and BTW; thanks Olivier for installing the SSL libs.
oops, you are right, my comment #4 relates to the validator (http://www.w3.org/Bugs/Public/show_bug.cgi?id=77) - sorry. Congrats to the validator implementation: it even works when my https is also protected with htaccess. When I try the same (https plus htaccess) with LinkChecker on URL https://www.privasphere.com/extProtoType/m4/threatRiskAnalysis.en.html, I get asked for a password for "Intranet" at validator.w3c.org which I obviously don't have. Also, it doesn't work for file URLs - couldn't that be enabled the same way as validator does it?
HTTP basic authentication seems to be broken in checklink, irrelevant of HTTPS. Logged as bug 122. When it asks for a password for some realm on some server, AFAICT there's no way we can affect the server part in the prompt. So the "Intranet" is actually on www.privasphere.com, not on validator.w3.org, and your normal intranet username and password should work (but this seems to be broken). Validator behaves the same way. The upload feature is already logged as bug 86. Closing this one again, this stuff is not related to HTTPS support in checklink.
Duh, I meant to say "Validator behaves the same way, but it is not broken".