We've just flipped the switch on www.postgresql.org to be served on https only. This has been done for a number of reasons:
We have not yet enabled HTTP Strict Transport Security, but will do so in a couple of days once we have verified all functionality. We have also not enabled HTTP/2 yet, this will probably come at a future date.
Please help us out with testing this, and let us know if you find something that's not working, by emailing the pgsql-www mailinglist.
There are still some other postgresql.org websites that are not available over https, and we will be working on those as well over the coming weeks or months.
The overhead of https is trivial on modern systems. Most likely you won't notice a difference.
A little week later have you noticed better ranking of your pages in Google searches?
I think it's more about not getting a lower score from Google, rather than actually increasing it. At this point it's not something we've studied the results of in detail yet.
Natural progression of all things Web/HTTP.
Kudos to you all PG guys and gals.
New comments can no longer be posted on this entry.
Forcing httpS, which requires more resources, for documentation (for instance), is a useless point :( But it's always good to be high ranked etc. thank you for the work done.