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
  • #53
Closed
Open
Created Sep 07, 2020 by Michał "rysiek" Woźniak@rysiek🔒Owner0 of 6 tasks completed0/6 tasks

Add/improve live examples to better illustrate functionality

We have an example page that only works after Samizdat is loaded (that is, after at least one visit to the Samizdat site. This is useful, but can be improved upon:

  • multiple different examples, showing how Samizdat behaves in different failure modes (depending on what we can simulate just with nginx configs, I guess)
    • 404 Not Found
    • 500 Internal Server Error and/or some other 50x errors
    • blackholing the request (request accepted, no data returned, but connection not terminated, just hanging)
    • response throttled down to a trickle (request accepted, but data returned so slow it's basically useless)
  • example of fetch()-less Service Worker to demonstrate possible privacy gain
Edited Sep 07, 2020 by Michał "rysiek" Woźniak
Assignee
Assign to
Time tracking