Broken links
-
So I know Digia is the commercial entity for QT, but supposedly Qt-Project is meant to handle the free / open source version....so where are you supposed to download the libs from? Because EVERY single link on https://qt-project.org/downloads 404's for me. I even tried to see if it was just the Windows downloads links that were dead, but no, all linux and mac links also 404 for the libs (5.0 and 4.8)
I saw the news posting that said some links might be broken...but seriously? The Downloads page?
-
I just tried a few different downloads from that page; they work for me.
Could you try again?
-
https://qt-project.org/qt4/source/qt-win-opensource-4.8.3-mingw.exe <--- 404
https://qt-project.org/qt4/source/qt-win-opensource-4.8.3-vs2008.exe <--- 404
https://qt-project.org/qt4/source/qt-win-opensource-4.8.3-vs2010.exe <--- 404
https://qt-project.org/qt4/source/qt-everywhere-opensource-src-4.8.3.tar.gz <--- 404
https://qt-project.org/qt4/source/qt-mac-opensource-4.8.3.dmg <--- 404
https://qt-project.org/qt4/source/qt-everywhere-opensource-src-4.8.3.tar.gz <--- 404
https://qt-project.org/qt4/source/qt-everywhere-opensource-src-4.8.3.zip <--- 404If a mod happens to pick up on this thread: browser is Firefox Nightly (also fails in Firefox 17) on Win7 x64. I can try it in IE but browser and OS shouldn't be an issue for following a link unless you guys are doing some screwed up stuff on the backend
-
Download links work in IE. So notice Admins: Download page links break in Firefox 17 and up, possibly earlier.
-
[quote author="ericg92" date="1353637973"]Download page links break in Firefox 17 and up, possibly earlier. [/quote]I can confirm it on Ubuntu & Firefox
-
I just visited that page using Firefox 17.0 (release version) in Windows 8, and the links are in this format now:
http://releases.qt-project.org/qt4/source/qt-win-opensource-4.8.3-mingw.exe
I was able to download the files successfully from Firefox 17.0. Please try again and see if the issue is resolved for you.
-
[quote author="JKSH" date="1353668629"]Please try again and see if the issue is resolved for you.[/quote] Yes, you are right :-) It works, at least using Firefox17 on Ubuntu
-
Alright, I've kind of sort of narrowed down the issue. I've got the HTTPS Everywhere Firefox addon installed from the EFF. When its configured to force HTTPS connections for Qt-project.org a redirect gets screwed up.
The actual download link is: releases.qt-project.org/qt4/source/qt-win-opensource-4.6.4-mingw.exe
And that is shown in the status bar if you mouse over the link. But if HTTPS is forced by HTTPS Everywhere, then even though the link is: releases.qt-project.org/qt4/source/qt-win-opensource-4.6.4-mingw.exe the user gets first sent to the actual link, page starts to load, and then gets redirected to: https://qt-project.org/qt4/source/qt-win-opensource-4.6.4-mingw.exe which 404's
Officially this is obviously a problem with HTTPS Everywhere but is there anything that can be done server side to elevate the redirect issue until it can be fixed? Considering that the EFF is trying to do some good with its addon and that they are pushing to have it installed more widely, it seems like a good idea to have a workaround.
Frankly I would've never thought to whitelist Qt-project from the addon if it wasnt for posting on here, and im not sure others will have the same inclination if they run into this problem.
-
Most of the Qt Project website is available via HTTPS (e.g. start browsing from https://qt-project.org/ ), just not the downloadable files.
If you have an idea for the website, you can submit a suggestion at https://bugreports.qt-project.org/secure/Dashboard.jspa (click "Create Issue", then choose the "Qt Project Website" project)
Personally though, it looks to me like a bug where the EFF's plugin picks the wrong subdomain -- "Another poster reported":https://qt-project.org/forums/viewthread/21044/ that the HTTP url http://bugreports.qt-project.org gets translated to https://qt-project.org . In this case, the server can't be expected to know which page the client is actually requesting; no server-side workarounds are possible.
Have you filed a big report with the EFF?
-
Yes I have filed an issue at the bug tracker for HTTPS Everywhere, with a link back to this forum thread. Hopefully something will come from it. but we'll see. Oh well, at least I've got the files I need and know how to workaround the problem in the future. Thanks guys!
