Now that we can use the certificates of Lets encrypt, many wikis will move to https in stead of http.
However, the RSS and Atom-feeds are still pointing at http
Is there a way to configure the RSS- and Atomfeeds to be pointing to https://... ?
Now that we can use the certificates of Lets encrypt, many wikis will move to https in stead of http.
However, the RSS and Atom-feeds are still pointing at http
Is there a way to configure the RSS- and Atomfeeds to be pointing to https://... ?
Wouldn't use the
//in the URL, to make the URL protocol relative, solve the problem? It seems to be already used, but if you ask this question, this means that the rss feed does not use it. Now someone has to track how the feed url is generated, and why it does not use this protocol-relutive URL (sorry, I will not do this myself: I would not find the time to do so these days).-- Louis
IkiWiki already uses relative (
../foo/), hostname-relative (/foo) or protocol-relative (//example.com/foo/) URLs wherever it can. However, not everything is allowed to be relative: in particular, more or less everything in RSS has to be absolute, either because the specification says so, or because in practice RSS consumers usually get relative URLs wrong. When we generated XHTML 1.0,<base href=... />had to be absolute too, but now that we always generate HTML 5 it's relative, so RSS is one of the few places the fullurlandcgiurlare used.If you have a certificate that's trusted by "normal" browsers (like LetsEncrypt), then there's no disadvantage in changing your
urlandcgiurlto both behttps://..., and rebuilding your wiki. At this point I would only recommend using plainhttp://if you either have no certificate, or a self-signed or otherwise not-universally-trusted certificate for a non-public website.Because IkiWiki mostly outputs relative URLs, accesses via
httpwill stay onhttp, unless you also reconfigure your web server (not specific to IkiWiki, for instance if you use Apache see RedirectSSL on the Apache wiki.