The VideoLAN Forums

I could not find the relevant mailing list, therefore I post this here. If you know how to, please relate this to the relevant people.

Few pages on the main web-site http://www.videolan.org has a few pages with HTTP links, although those pages and resources are available over HTTPS. This creates a potential problem (user leaving secure HTTPS) and breaks Chrome's security validation (no green padlock next on the left of the address bar).

This issue is misleading people, like in https://forum.videolan.org/viewtopic.php?f=10&t=134384.

Here the pages without a padlock:

• The downloads page https://www.videolan.org/vlc/download-sources.html
• The VideoLAN Goodies page https://www.videolan.org/goodies.html

List of pages relying on or linking to HTTP resources, yet passing green padlock check:
List is in the comments because of limit of 5 URLs per post.

Issue and Fix:
The source and page links have "http://" hardwritten in, instead of "//".
Please note that HTTPS Everywhere from Electronic Frontier Foundation automatically rewrites the links to HTTPS (and everything works properly), so fix is as simple as replacing "http://" with "//".

If VideoLAN website is hosted somewhere on a public repo supporting pull requests, please let me know: I'll propose the changes directly there (to save both your and my time).

List of pages relying on or linking to HTTP resources, yet passing green padlock check (shortened):

• In the <header> the link to RSS feed uses HTTP, supports HTTPS
• The Thank You page http://www.videolan.org/thank_you.html uses HTTP, supports HTTPS:
• Facebook and Twitter are linked to with HTTP (but, of course, will upgrade to HTTPS)
  
  I realized that there are simply too many resources to list here (that would be spamming), so I'll stop here.
  
  P.S.: Is anyone reading this?

I think I have found the correct place for these edits on the VideoLAN GitLab pages: https://code.videolan.org/VideoLAN.org/websites.
I will try to implement these changes and get them approved. Unfortunately, I do not think I can delete the original post (except for "reporting" it), so I'll just leave it here. Sorry .

Some of the issues reported are now fixed.

Thank you very much!

Unfortunately, there are more issues. I would like to help and I believe the most efficient way is for me to propose the changes in the code and submit them for review (instead of listing them here and then checking that they were fixed). Is that possible? Also, I recently sent an email to <www-doc[AT]videolan.org>, I believe you are on it.

Sure.