diff options
| author |  Joey Hess <joey@kitenet.net> | 2013-03-09 01:58:07 -0400 |
|---|---|---|
| committer | Joey Hess <joey@kitenet.net> | 2013-03-09 01:58:07 -0400 |
| commit | e7a4d325d5bb4be30e7e8770c501629fc4107b52 (patch) | |
| tree | d12bdf1949ef836e479f0cdc32d0d7208f44e3af | |
| parent | ebc8a5a907de601f2b5d8c75d0c966b6d9f18b30 (diff) | |
verified that warp hang is due to faulty slowloris prevention timeout
| -rw-r--r-- | doc/bugs/webapp_hang.mdwn | 5 |
1 files changed, 4 insertions, 1 deletions
diff --git a/doc/bugs/webapp_hang.mdwn b/doc/bugs/webapp_hang.mdwn index dde19c3e3..0f9af5b28 100644 --- a/doc/bugs/webapp_hang.mdwn +++ b/doc/bugs/webapp_hang.mdwn @@ -28,7 +28,10 @@ Hypotheses: repeated hits to update the alerts? I added a settingsOnException handler that logs all exceptions, and ThreadKilled is happening several times. The only place in Warp that kills threads is due to a timeout installed - for that. + for that. + + **Verified** Bug filed upstream: <https://github.com/yesodweb/wai/issues/146> + * Something deep in git-annex, such as the inotidy code, could be preventing a web server thread from running. But then why do other tabs and other web browsers work while it's stuck? |