Skip to content
GitLab
  • Menu
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • samizdat samizdat
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 34
    • Issues 34
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • Michał "rysiek" Woźniak
  • samizdatsamizdat
  • Issues
  • #65
Closed
Open
Created Sep 19, 2020 by Michał "rysiek" Woźniak@rysiek🔒Owner

Reasonable timeout for `plugin.fetch()` in the ServiceWorker

Currently the ServiceWorker just runs any plugin (including the initial HTTPS fetch()) without any explicit timeouts. This is sub-optimal, for example when:

  • the site is censored by DROPing the packets on some firewall (instead of rejecting them);
  • the site is experiencing technical issues and effectively takes forever to load;
  • any of the plugins (looking at you, IPFS) takes inordinate amount of time to return either the content, or an error.

We need to be able to wait for some time, but then just go with another plugin, before the browser times out on us.

Assignee
Assign to
Time tracking