This repository was archived by the owner on Dec 18, 2018. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 523
Active Keep-Alive connections are not closed before shutting down the loop #62
Comments
Tragetaschen
pushed a commit
to Tragetaschen/KestrelHttpServer
that referenced
this issue
Feb 11, 2015
Tragetaschen
pushed a commit
to Tragetaschen/KestrelHttpServer
that referenced
this issue
Feb 20, 2015
Tragetaschen
pushed a commit
to Tragetaschen/KestrelHttpServer
that referenced
this issue
Feb 20, 2015
Tragetaschen
pushed a commit
to Tragetaschen/KestrelHttpServer
that referenced
this issue
Feb 20, 2015
Tragetaschen
pushed a commit
to Tragetaschen/KestrelHttpServer
that referenced
this issue
Feb 20, 2015
Tragetaschen
pushed a commit
to Tragetaschen/KestrelHttpServer
that referenced
this issue
Feb 24, 2015
Tragetaschen
pushed a commit
to Tragetaschen/KestrelHttpServer
that referenced
this issue
Feb 24, 2015
Tragetaschen
pushed a commit
to Tragetaschen/KestrelHttpServer
that referenced
this issue
Mar 14, 2015
Tragetaschen
pushed a commit
to Tragetaschen/KestrelHttpServer
that referenced
this issue
Mar 14, 2015
Tragetaschen
pushed a commit
to Tragetaschen/KestrelHttpServer
that referenced
this issue
Apr 30, 2015
11 tasks
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I'm currently tracking down ways the loop resource handle's Finalizer from #60 is called instead of the Dispose method.
One occurrence is when there are still active
Connection: Keep-Alive
connections that a browser could (and will) reuse. Those are still active handles on the loop and should be actively closed instead of implicitly through the shutdown logic.The text was updated successfully, but these errors were encountered: