Closed
Bug 924824
Opened 13 years ago
Closed 13 years ago
Chrome blocks Firefox download due to unsecure content on /new on https
Categories
(www.mozilla.org :: Pages & Content, defect)
Tracking
(Not tracked)
VERIFIED
FIXED
People
(Reporter: agibson, Unassigned)
References
Details
(Whiteboard: [kb=1150753] )
Steps to reproduce:
Chrome version 30.0.1599.69
1.) Visit: https://www.mozilla.org/en-US/firefox/new/
2.) Click the green download button
Chrome will block the download, reporting the following console warning:
[blocked] The page at https://www.mozilla.org/en-US/firefox/new/#download-fx ran insecure content from http://download.cdn.mozilla.net/pub/mozilla.org/firefox/releases/24.0/mac/en-US/Firefox%2024.0.dmg.
Expected results:
Chrome should download Firefox.
Looking at the page source, both the green button and the direct download link point to:
https://download.mozilla.org/?product=firefox-24.0&os=osx&lang=en-US
So perhaps there is some kind of redirect issue going on here?
This would have been picked up the last time we pushed an update to this page, so has something else changed?
| Reporter | ||
Updated•13 years ago
|
Summary: Chrome blocks Firefox download due to unsecure content on /new → Chrome blocks Firefox download due to unsecure content on /new on https
Comment 1•13 years ago
|
||
I can confirm that there is a 302 redirect:
curl -A "User-Agent': 'User-Agent': 'Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:17.0) Gecko/17.0 Firefox/17.0" --header "Accept-Language: cs" -LIs https://download.mozilla.org/?product=firefox-24.0&os=osx&lang=en-US
$ HTTP/1.1 302 Found
Server: Apache
X-Backend-Server: bouncer3.webapp.phx1.mozilla.com
Cache-Control: max-age=15
Content-Type: text/html; charset=UTF-8
Date: Wed, 09 Oct 2013 09:49:08 GMT
Location: http://download.cdn.mozilla.net/pub/mozilla.org/firefox/releases/24.0/win32/en-US/Firefox%20Setup%2024.0.exe
Transfer-Encoding: chunked
Connection: Keep-Alive
Set-Cookie: dmo=10.8.81.219.1381312148651398; path=/; expires=Thu, 09-Oct-14 09:49:08 GMT
X-Cache-Info: caching
That's a bug in our bouncer or cdn I believe, so probably for another Bugzilla product/component.
Severity: normal → major
Comment 2•13 years ago
|
||
CCing Daniel from webops as I think he has some knowledge about the CDN and laura in case the bug is on the bouncer code
| Reporter | ||
Comment 3•13 years ago
|
||
Thanks, Pascal!
Comment 4•13 years ago
|
||
The link is only https if you go to https://www.mozilla.org/, if you go to http://www.mozilla.org/ it's https and is redirected appropriately.
Perhaps the link in the page should be forced to http, I'm unclear if bouncer/CDNs do https at all.
Comment 5•13 years ago
|
||
s/it's https/it's http/
| Reporter | ||
Comment 6•13 years ago
|
||
I first noticed this when trying on dev/stage - which both force https.
Prod does not force https, but you can still visit the page using either.
Comment 7•13 years ago
|
||
Ok, so my point remains that I don't know if the bouncer/CDNs do https so perhaps the download link should specifically be http?
Comment 9•13 years ago
|
||
pir@wedge> telnet download.cdn.mozilla.net 443
Trying 69.16.175.10...
telnet: connect to address 69.16.175.10: Connection refused
Trying 69.16.175.42...
telnet: connect to address 69.16.175.42: Connection refused
telnet: Unable to connect to remote host
Since download.cdn.mozilla.net doesn't listen on port 443 I think it's fairly safe to say we shouldn't be handing out https links that end up there.
Comment 10•13 years ago
|
||
Digging Bugzilla, I found that the change to https for download links was requested in bug 796057 for the stub installer project (which is now the default installer I think), in case it helps.
Comment 11•13 years ago
|
||
We don't use download.mozilla.org any more.
| Reporter | ||
Comment 12•13 years ago
|
||
(In reply to Peter Radcliffe [:pir] from comment #7)
> Ok, so my point remains that I don't know if the bouncer/CDNs do https so
> perhaps the download link should specifically be http?
If the download link was specifically http, would it not then still get blocked over https?
Comment 13•13 years ago
|
||
I don't understand the question. Why would an http link get blocked?
Comment 14•13 years ago
|
||
In https://bugzilla.mozilla.org/show_bug.cgi?id=796057#c2 :jakem raised this exact possibility for https links being redirected to http.
This link shouldn't be https.
| Reporter | ||
Comment 15•13 years ago
|
||
(In reply to Peter Radcliffe [:pir] from comment #13)
> I don't understand the question. Why would an http link get blocked?
Well, if I visit:
https://www-dev.allizom.org/en-US/firefox/new/
and then change the green button download link to:
http://download.mozilla.org/?product=firefox-24.0&os=osx&lang=en-US
When clicking the download button, I still get this?
[blocked] The page at https://www-dev.allizom.org/en-US/firefox/new/#download-fx ran insecure content from http://download.mozilla.org/?product=firefox-24.0&os=osx&lang=en-US.
Comment 16•13 years ago
|
||
No idea. Not my area of expertise.
If all links from mozilla.org need to be https then to fix this all CDNs will need to be switched to something that uses https, as :jakem mentions: https://bugzilla.mozilla.org/show_bug.cgi?id=796057#c2
This isn't a bouncer bug. It isn't a config error. The CDN doesn't do https so we can't redirect https -> https... so either the download page needs to be http or someone needs to spend a lot more money on a CDN that will do https.
Comment 17•13 years ago
|
||
(In reply to Alex Gibson [:agibson] from comment #15)
> When clicking the download button, I still get this?
>
> [blocked] The page at
> https://www-dev.allizom.org/en-US/firefox/new/#download-fx ran insecure
> content from
> http://download.mozilla.org/?product=firefox-24.0&os=osx&lang=en-US.
To be perfectly clear, what you're seeing here is browser behaviour : any time an HTTPS link is re-directed to an HTTP link, Chrome will throw that error. There are two possible solutions :
1. Modify the download links such that they do not perform this 302 (i.e. HTTP URLs only).
2. Negotiate a new and much more expensive contract with our CDN partners in order to allow HTTPS content delivery.
The latter of these two solutions is outside the scope of this bug entirely and can be dismissed for the time being. This leaves the former of the two - modifying the download URLs - as the only possible way to avoid the undesirable browser behaviour at this time.
| Reporter | ||
Comment 18•13 years ago
|
||
(In reply to Daniel Maher [:phrawzty] from comment #17)
> To be perfectly clear, what you're seeing here is browser behaviour : any
> time an HTTPS link is re-directed to an HTTP link, Chrome will throw that
> error. There are two possible solutions :
> 1. Modify the download links such that they do not perform this 302 (i.e.
> HTTP URLs only).
> 2. Negotiate a new and much more expensive contract with our CDN partners in
> order to allow HTTPS content delivery.
>
> The latter of these two solutions is outside the scope of this bug entirely
> and can be dismissed for the time being. This leaves the former of the two
> - modifying the download URLs - as the only possible way to avoid the
> undesirable browser behaviour at this time.
What I'm questioning, is that modifying the download url's to be all http is not going to solve the issue here? The issue is that the page is/can be viewed on https, unless I am mistaken here?
Comment 19•13 years ago
|
||
:agibson I don't understand your question.
| Reporter | ||
Comment 20•13 years ago
|
||
Sorry, perhaps there is something I'm missing here :)
But if I view the page on 'https', and click the download link when it is changed to 'http', I'm still seeing Chrome block the download?
Comment 21•13 years ago
|
||
If that is true then we can't fix both problems without aforementioned spending huge amounts of money on a new CDN contract, which I can't fix.
| Reporter | ||
Comment 22•13 years ago
|
||
Ok think I may understand why I'm seeing the download block even when the link is http:
The page is using an iframe to trigger the download, hence why the content blocker kicks in.
If we can't fix/change the CDN redirect, then this page may have to use an alternative means to trigger the download?
Comment 23•13 years ago
|
||
The iframe was recently added to resolve issues on IE. Also, https://d.m.o links were changed on mozilla.org on purpose because the security group didn't want us serving downloads via http any longer and to resolved mixed content issue. If CDNs redirect to an http, then this doesn't help anything. It seems pretty sad that we spent time going to https, resolved http content on the site, and we wanted to do SSL CDNs to find out the CDNs are not SSL and thus the whole SSL project on mozilla.org is blocked.
Comment 24•13 years ago
|
||
What if /firefox/new/ redirected to http always and the link to d.m.o. was http so eliminate mixed content since the CDNs were not SSL? I also thought we *had* to have a SSL CDN for stub installer builds as described in bug 795440.
What if we just use https for serving up stub installer and http for non stub installers?
Comment 25•13 years ago
|
||
Raymond: can you test this for us? Please use https://www.mozilla.org/en-US/firefox/new/ as the test.
Comment 26•13 years ago
|
||
(In reply to Chris More [:cmore] from comment #25)
> Raymond: can you test this for us? Please use
> https://www.mozilla.org/en-US/firefox/new/ as the test.
http://www.mozilla.org/en-US/firefox/new/ was not blocked for me on Version 30.0.1599.69 on Mac and Windows
Comment 27•13 years ago
|
||
The iframe was added to prevent cancelling CSS asset downloads when the Firefox download started.
Comment 28•13 years ago
|
||
Filed https://bugzilla.mozilla.org/show_bug.cgi?id=925121
Jakem explains further in comment # 2 https://bugzilla.mozilla.org/show_bug.cgi?id=925121#c2
Updated•13 years ago
|
Whiteboard: [kb=1150753]
Comment 29•13 years ago
|
||
Comment 30•13 years ago
|
||
Raymond, this is now up on https://www-demo3.allizom.org/en-US/firefox/new/
Can you help us test this?
Comment 31•13 years ago
|
||
Tried this in Chrome and various versions of IE. It worked fine for me in all cases.
https://www-demo3.allizom.org/en-US/firefox/new/
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
Comment 32•13 years ago
|
||
Commit pushed to master at https://github.com/mozilla/bedrock
https://github.com/mozilla/bedrock/commit/fc11a9f4855f1d361ecf6e23667d01c504ffd897
Merge pull request #1319 from gauthierm/fix-blocked-download-iframe-chrome
Bug 926701, 924824: Use window.location instead of iframe to trigger download.
Comment 33•13 years ago
|
||
fixed on stage https://www-dev.allizom.org/en-US/firefox/new/
Comment 34•13 years ago
|
||
Fixed on Chrome https://www.mozilla.org/en-US/firefox/new/#download-fx and https://www.mozilla.org/en-US/firefox/new/
Status: RESOLVED → VERIFIED
You need to log in
before you can comment on or make changes to this bug.
Description
•