Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • Trac Trac
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Issues 246
    • Issues 246
    • List
    • Boards
    • Service Desk
    • Milestones
  • Monitor
    • Monitor
    • Metrics
    • Incidents
  • Analytics
    • Analytics
    • Value stream
  • Wiki
    • Wiki
  • Activity
  • Create a new issue
  • Issue Boards
Collapse sidebar
  • Legacy
  • TracTrac
  • Issues
  • #32716

Closed (moved)
(moved)
Open
Created Dec 10, 2019 by Cecylia Bocovich@cohosh

Understand where gettor distribution providers are blocked

We should get a better understanding of where our different gettor providers are blocked. Right now we use four different providers:

  • gitlab.com
  • github.com
  • archive.org
  • docs.google.com

However, some of these domains resolve to a different URL in the process of downloading the file. For example, binaries uploaded to github used to retrieved from raw.githubusercontent.com and now it redirects to github-production-release-asset-2e65be.s3.amazonaws.com.

Perhaps we can use OONI data to stay on track of when gettor becomes unavailable due to blocking these URLs?

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking