{"action":"opened","issue":{"url":"https://api.github.com/repos/Alamofire/Alamofire/issues/615","labels_url":"https://api.github.com/repos/Alamofire/Alamofire/issues/615/labels{/name}","comments_url":"https://api.github.com/repos/Alamofire/Alamofire/issues/615/comments","events_url":"https://api.github.com/repos/Alamofire/Alamofire/issues/615/events","html_url":"https://github.com/Alamofire/Alamofire/issues/615","id":97492581,"number":615,"title":"304 HTTP Status code - ignore cached response / handle manually","user":{"login":"orschaef","id":1017995,"avatar_url":"https://avatars.githubusercontent.com/u/1017995?v=3","gravatar_id":"","url":"https://api.github.com/users/orschaef","html_url":"https://github.com/orschaef","followers_url":"https://api.github.com/users/orschaef/followers","following_url":"https://api.github.com/users/orschaef/following{/other_user}","gists_url":"https://api.github.com/users/orschaef/gists{/gist_id}","starred_url":"https://api.github.com/users/orschaef/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/orschaef/subscriptions","organizations_url":"https://api.github.com/users/orschaef/orgs","repos_url":"https://api.github.com/users/orschaef/repos","events_url":"https://api.github.com/users/orschaef/events{/privacy}","received_events_url":"https://api.github.com/users/orschaef/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":0,"created_at":"2015-07-27T15:41:27Z","updated_at":"2015-07-27T15:41:27Z","closed_at":null,"body":"Hi,\r\n\r\nI have the following problem:\r\n\r\nWe fire requests against a sync api. If we have any server changes we get a **200** with the according json which includes the modified entities.\r\nIf we have no changes we correctly get a **304**. But Alamofire caches the latest 200 response and provides it. So it is impossible to know if we got a 304 (because that would mean we don't have to do anything). \r\n\r\nWe could disable the cache, but that would mean we lose the 304 caching convenience for all the other requests that have nothing to do with syncing.\r\n\r\n**Recommendation**: Maybe it would be useful to manually disable/enable the cache for every request (is that somehow possible?) or to provide something like 'original status code'.\r\nThat are just the first thoughts, maybe you come up with a better solution.\r\n\r\nOr did I miss something?"}}