Bug 1140 - Download page should not use https links
Summary: Download page should not use https links
Status: RESOLVED FIXED
Alias: None
Product: Websites
Classification: Unclassified
Component: www.mageia.org (show other bugs)
Version: trunk
Hardware: All Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Atelier Team
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-05-04 23:30 CEST by Nicolas Vigier
Modified: 2011-05-05 00:18 CEST (History)
3 users (show)

See Also:
Source RPM:
CVE:
Status comment:


Attachments
Fix to remove https (552 bytes, patch)
2011-05-05 00:18 CEST, Michael Scherer
Details | Diff

Description Nicolas Vigier 2011-05-04 23:30:28 CEST
On download page :
http://www.mageia.org/en/downloads/dl.php?product=mageia-1-beta2-dvd-i586

A random mirror is selected. Sometimes, distrib-coffee.ipsl.jussieu.fr is selected with https. However, the SSL certificate is not accepted by firefox, so it display a warning page. As the download is started automatically, the warning page is displayed after 2 seconds, and it is not possible to select other mirrors.

As using https in random is not very useful, I think it should not be removed.
Comment 1 Michael Scherer 2011-05-05 00:01:53 CEST
We also need to filter rsync mirror from the list as a web browser may have some trouble for that.

CC: (none) => misc

Comment 2 Romain d'Alverny 2011-05-05 00:09:00 CEST
Fixed (r407), in production. rsync is already filtered out.

Status: NEW => RESOLVED
CC: (none) => rdalverny
Resolution: (none) => FIXED

Comment 3 AL13N 2011-05-05 00:17:06 CEST
perhaps, if we have a https mirror, it should be with a valid certificate?

CC: (none) => maarten.vanraes

Comment 4 Michael Scherer 2011-05-05 00:17:38 CEST
But not https :
Comment 5 Michael Scherer 2011-05-05 00:18:04 CEST
Created attachment 354 [details]
Fix to remove https
Comment 6 Michael Scherer 2011-05-05 00:18:51 CEST
Also, on epiphany, ftp will produce a error ( "current emplacement not mounted" )

And epiphany do not complain on https :)

Note You need to log in before you can comment on or make changes to this bug.