{"action":"created","issue":{"url":"https://api.github.com/repos/icing/mod_h2/issues/116","repository_url":"https://api.github.com/repos/icing/mod_h2","labels_url":"https://api.github.com/repos/icing/mod_h2/issues/116/labels{/name}","comments_url":"https://api.github.com/repos/icing/mod_h2/issues/116/comments","events_url":"https://api.github.com/repos/icing/mod_h2/issues/116/events","html_url":"https://github.com/icing/mod_h2/issues/116","id":177153683,"number":116,"title":"mod_h2 breaks wordpress ","user":{"login":"chrcoluk","id":8260578,"avatar_url":"https://avatars.githubusercontent.com/u/8260578?v=3","gravatar_id":"","url":"https://api.github.com/users/chrcoluk","html_url":"https://github.com/chrcoluk","followers_url":"https://api.github.com/users/chrcoluk/followers","following_url":"https://api.github.com/users/chrcoluk/following{/other_user}","gists_url":"https://api.github.com/users/chrcoluk/gists{/gist_id}","starred_url":"https://api.github.com/users/chrcoluk/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/chrcoluk/subscriptions","organizations_url":"https://api.github.com/users/chrcoluk/orgs","repos_url":"https://api.github.com/users/chrcoluk/repos","events_url":"https://api.github.com/users/chrcoluk/events{/privacy}","received_events_url":"https://api.github.com/users/chrcoluk/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":2,"created_at":"2016-09-15T11:37:06Z","updated_at":"2016-09-15T11:44:20Z","closed_at":null,"body":"So on protocol 1.1. if I update wordpress by clicking upgrade in the web gui, after the upgrade finishes it will either load a success or failed page depending if the upgrade worked or not.\r\n\r\nIf I do the same with over http/2 then at the end of the upgrade process I get a \"connection has been closed\" error in the browser, regardless if the upgrade worked or not, it doesnt kill the upgrade so http/2 waits long enough but then fails to load the page at the end.\r\n\r\nI did look to toggle some timeouts but it seems h2timeout etc. no longer exist?"},"comment":{"url":"https://api.github.com/repos/icing/mod_h2/issues/comments/247306043","html_url":"https://github.com/icing/mod_h2/issues/116#issuecomment-247306043","issue_url":"https://api.github.com/repos/icing/mod_h2/issues/116","id":247306043,"user":{"login":"icing","id":15102,"avatar_url":"https://avatars.githubusercontent.com/u/15102?v=3","gravatar_id":"","url":"https://api.github.com/users/icing","html_url":"https://github.com/icing","followers_url":"https://api.github.com/users/icing/followers","following_url":"https://api.github.com/users/icing/following{/other_user}","gists_url":"https://api.github.com/users/icing/gists{/gist_id}","starred_url":"https://api.github.com/users/icing/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/icing/subscriptions","organizations_url":"https://api.github.com/users/icing/orgs","repos_url":"https://api.github.com/users/icing/repos","events_url":"https://api.github.com/users/icing/events{/privacy}","received_events_url":"https://api.github.com/users/icing/received_events","type":"User","site_admin":false},"created_at":"2016-09-15T11:44:20Z","updated_at":"2016-09-15T11:44:20Z","body":"@chrcoluk there is a fix in regard to timeout handling in mod_http2 v1.5.13. The normal ```Timeout``` directive was applied to ongoing requests which should not. It should only apply to IO operations. That has been fixed.\r\n\r\nYour problem sounds like it matches that. Try either to raise ```Timeout``` to something large enough or deploy a newer module from here."}}
{"actor":{"display_login":"icing"}}