Skip to content
GitLab
    • GitLab: the DevOps platform
    • Explore GitLab
    • Install GitLab
    • How GitLab compares
    • Get started
    • GitLab docs
    • GitLab Learn
  • Pricing
  • Talk to an expert
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
    • Switch to GitLab Next
    Projects Groups Topics Snippets
  • Register
  • Sign in
  • libresilient libresilient
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributor statistics
    • Graph
    • Compare revisions
  • Issues 32
    • Issues 32
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 1
    • Merge requests 1
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Package Registry
    • Container Registry
    • Infrastructure Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • Michał "rysiek" Woźniak
  • libresilientlibresilient
  • Issues
  • #53
Closed
Open
Issue created Jun 17, 2022 by Michał "rysiek" Woźniak@rysiekpl🔒Owner

"Reverse-scoping": make it possible to remove certain locations from LR's scope

Currently it is possible to scope LR to a particular sub-directory of a website, but it is impossible to remove certain directories that are within the scope from it.

Consider a website like this:

/
 - admin/
 - blog/
 - assets/

It is possible to scope LR only to either /blog/ or /assets/, but it's currently impossible to scope LR to / but keep /admin/ out of scope, or to scope it only to /admin/ and /assets/ but leave /blog/ out.

This is directly caused by the scope option of the ServiceWorkerContainer.register() method being a string.

What LR could do about this is have its internal way of defining separate config branches for each sub-directory of the scoped directory, so that while the service worker is still registered and scoped to them, a directory where we do not want any special handling could be set to only go through standard fetch().

Edited Oct 08, 2022 by Michał "rysiek" Woźniak
Assignee
Assign to
Time tracking