(from pcervinka's email):
It will be harder and harder to find pages with http only. Almost all
known/usable sites redirect from http to https.
What about keep it as it is? Test will use http, server redirects to
https. I think this can be used as valid (because http works and resultof working http is redirect to https)
Yeah, I hear you, with the search engine companies and other big players of the web industry requiring and/or giving advantage to secure sites, it will be more and more rare to find a suitable http website for this test.
Personally, however, I believe that the tests should be straightforward and semantic, and I'm not that keen on the idea of establishing that the http protocol works properly on the grounds that it redirects correctly to https (on this particular website).
I have found out that BBC is planning to stick to the unsecured http protocol in their news archive, at least for the foreseeable future, as explained in their official blog: http://www.bbc.co.uk/blogs/internet/entries/f6f50d1f-a879-4999-bc6d-6634a71e2e60
"Sites and content we consider ‘archival’ that involve no signing in or personalisation, such as the News Online archive on news.bbc.co.uk, will remain HTTP-only. This is due to the cost we’d incur processing tens of millions of old files to rewrite internal links to HTTPS when balanced against the benefit."
So maybe the BBC news website could work for now.
On the other hand, I like your suggestion in the sense that we could consider extending this test module with the http>https redirection as a case on its own right, since it is a very common practice on the web for a lot of websites.