{"action":"opened","issue":{"url":"https://api.github.com/repos/gobblejs/gobble/issues/126","repository_url":"https://api.github.com/repos/gobblejs/gobble","labels_url":"https://api.github.com/repos/gobblejs/gobble/issues/126/labels{/name}","comments_url":"https://api.github.com/repos/gobblejs/gobble/issues/126/comments","events_url":"https://api.github.com/repos/gobblejs/gobble/issues/126/events","html_url":"https://github.com/gobblejs/gobble/issues/126","id":186169515,"number":126,"title":"Stale content due to lack of Cache-Control headers (dev server)","user":{"login":"msegado","id":1887854,"avatar_url":"https://avatars.githubusercontent.com/u/1887854?v=3","gravatar_id":"","url":"https://api.github.com/users/msegado","html_url":"https://github.com/msegado","followers_url":"https://api.github.com/users/msegado/followers","following_url":"https://api.github.com/users/msegado/following{/other_user}","gists_url":"https://api.github.com/users/msegado/gists{/gist_id}","starred_url":"https://api.github.com/users/msegado/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/msegado/subscriptions","organizations_url":"https://api.github.com/users/msegado/orgs","repos_url":"https://api.github.com/users/msegado/repos","events_url":"https://api.github.com/users/msegado/events{/privacy}","received_events_url":"https://api.github.com/users/msegado/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":0,"created_at":"2016-10-30T22:29:45Z","updated_at":"2016-10-30T22:29:45Z","closed_at":null,"body":"The Gobble dev server doesn't set any cache-control headers, which can lead to browsers caching content during development (and some related head-scratching about why the latest changes aren't showing up). Should be easy to fix by adding something like the following to all the server responses:\r\n\r\n```js\r\nresponse.setHeader( 'Cache-Control', 'no-cache' );\r\n```"}}
{"actor":{"display_login":"msegado"}}