Skip to content

GitLab

  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • P publickey-auth-feathers-nuxt-sockets
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 13
    • Issues 13
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • Indienet
  • Spikes
  • Security
  • publickey-auth-feathers-nuxt-sockets
  • Issues
  • #31

Closed
Open
Created Mar 13, 2018 by Aral Balkan@aralOwner

When two non-private tabs/windows are open, signing out of one doesn’t cut off the socket connection on the other

## To reproduce

  1. Open two non-private tabs or windows
  2. Sign in on both
  3. Sign out on one

## What should happen

Both should immediately be signed out and the socket connections closed.

## What actually happens

Only the browser tab/window that you signed out of has its socket connection terminated immediately. The other tab/window continues to get messages.

If you refresh the other tab/window, only then are you forwarded to the sign-in route.

Assignee
Assign to
Time tracking

Like this? Fund us! Your patronage helps keep us independent and going.