-
Notifications
You must be signed in to change notification settings - Fork 2.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Error: The 'Referer' header must be modified using the appropriate property or method. #2026
Comments
This is most likely a consequence of pbatard/Fido#41 and its fix where we added I guess that older versions of PowerShell, such as the one used by Windows 7, do not support using I've had a quick look to see if there was a specific "old PowerShell" way of doing this, but couldn't find any. Now of course, your problem becomes is that I no longer support Windows 7 in any way shape or form, so, unless somebody else wants to spend their time investigating and proposing a fix, I am currently planning to drop the ISO download functionality of Rufus on Windows 7 platforms that use a version of PowerShell that is incompatible with setting the referrer as a result of this issue, since you won't be able to download much of anything... I have also opened pbatard/Fido#44, to give people who are interested in fixing this a chance, since I all I am planning to do at this stage, is disable Fido downloads on any platform that does not meet the PowerShell requirements for |
I'll have a look at this tomorrow. |
Sidenote: I'm also curious as to whether the "referer" header is absolutely necessary? Do the Microsoft download servers block (or somehow cripple) the ISO-downloads if the referer-header is not set, or if one simply goes directly to attempt the download with the direct ISO-link? And on a related note, if one chooses the option to "Download via browser" in the settings dialog, does the referer-header somehow get passed to the browser in this case? |
Yup. Per pbatard/Fido#41, if you don't set the referer in the header, then the POST query that provides the download links will be rejected by the Microsoft servers. That's the whole reason we added the referer in the first place, and why the script no longer works for people who use a PowerShell version that doesn't support Note that we need to issue two requests before we can get the ISO download links and that the download links themselves don't need anything special to work. But to get to these links, you must get the Microsoft servers to answer the requests, and you need a referer set.
Again, there's no need for a referer or anything special once you get the download links. |
Roger that. Thanks for the clarifications, Pete. |
For your reference, from the log above:
|
OK. Roger that. Thank you for the additional clarifications, again. |
Closed in pbatard/Fido@9beb231 |
Thank you so much -- for managing to find a backward-compatibility fix for this! In other words, I can confirm that Windows 10/11 ISO downloads now work flawlessly with Rufus 3.20 (via the latest fido.ps1 script), even on Windows 7 SP1. (And forgive me for being so "entrenched" that I still need Windows 7 on some of my systems.) |
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue if you think you have a related problem or query. |
Checklist
<FULL LOG>
below.Rufus version: x.y.z
- I have NOT removed any part of it.Additionally (if applicable):
(✓)
button to compute the MD5, SHA1 and SHA256 checksums, which are therefore present in the log I copied. I confirmed, by performing an internet search, that these values match the ones from the official image.Issue description
I was trying to download a Windows 10 ISO-image with Rufus on Windows 7 SP1, 64-bit, Ultimate-Edition.
I got as far as selecting the Version, Release, Edition and Language options (as shown below).
At this point, when clicking on "Continue", Rufus came up with an ERROR message, stating:
This completely prevented me from accessing the ISO-downloads, but gave me no clue as to which component of my Windows 7 SP1 installation might have failed to set the "referer" header.
I can only surmise that this could be related to the older version of Internet Explorer on my Windows 7 setup -- but then again, I have also read elsewhere that the current version of the downloader script does not rely on IE.
Also, this error does not come up on my Windows 10 setup at all. In other words, on my Windows 10 setup, RUFUS downloads ISO-images just fine. I have been using it as a workaround, but obviously it'd be "nice to know" how to fix this and what's causing it. I guess there must be some component of Windows 7 that I should try to update.
Also, technically this problem is propably related to the FIDO PowerShell script to download Windows ISOs, but since I'm using it via RUFUS decided I'd post the issue here at the RUFUS issue tracker.
Log
The text was updated successfully, but these errors were encountered: