Skip to content
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

[Bug] scoop should try other URLs and continue update after a 403 error #5035

Closed
val1984 opened this issue Jul 4, 2022 · 3 comments
Closed
Labels

Comments

@val1984
Copy link

val1984 commented Jul 4, 2022

Bug Report

Current Behavior

I am behind a company proxy which blocks some downloads with ever changing rules and when I scoop update *, scoop will stop updating once it encounters a 403 error.

Expected Behavior

I would expect scoop to carry on after a 403 error:

  • Try next URL for current package
  • Update next package if there is no alternate URL for current package

Additional context/output

❯ scoop update *
autohotkey: 1.1.33.10 -> 1.1.34.03
groovy: 3.0.9 -> 4.0.3
Updating 2 outdated apps:
Updating 'autohotkey' (1.1.33.10 -> 1.1.34.03)
Downloading new version
OperationStopped: C:\Users\myuser\scoop\apps\scoop\current\lib\install.ps1:107
Line |
 107 |          throw $e
     |          ~~~~~~~~
     | The remote server returned an error: (403) URLBlockedExtended.
>

Possible Solution

System details

Windows version:
10 20H2

OS architecture:
64bit

PowerShell version:
7.2.5

Scoop Configuration

{
  "lastupdate": "2022-07-04T13:31:21.2168552+02:00",
  "proxy": "currentuser@default",
  "SCOOP_REPO": "https://github.com/ScoopInstaller/Scoop",
  "SCOOP_BRANCH": "master",
  "shim": "kiennq"
}
@rashil2000
Copy link
Member

  • Try next URL for current package

Not recommended since the install procedure might have a dependency on that downloaded item.

  • Update next package if there is no alternate URL for current package

Tracked here #4135

@val1984
Copy link
Author

val1984 commented Jul 5, 2022

  • Try next URL for current package

Not recommended since the install procedure might have a dependency on that downloaded item.

My bad, I thought having multiple URLs was a way to specify a mirror.

  • Update next package if there is no alternate URL for current package

Tracked here #4135

Thank you for the link!

@rashil2000
Copy link
Member

rashil2000 commented Jul 5, 2022

Fallback mirrors are being tracked here #4264

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants