{"action":"opened","issue":{"url":"https://api.github.com/repos/ryancramerdesign/ProcessWire/issues/1189","labels_url":"https://api.github.com/repos/ryancramerdesign/ProcessWire/issues/1189/labels{/name}","comments_url":"https://api.github.com/repos/ryancramerdesign/ProcessWire/issues/1189/comments","events_url":"https://api.github.com/repos/ryancramerdesign/ProcessWire/issues/1189/events","html_url":"https://github.com/ryancramerdesign/ProcessWire/issues/1189","id":78857561,"number":1189,"title":"Disabling cache for *any* GET or POST params, not just specific ones","user":{"login":"teppokoivula","id":1252021,"avatar_url":"https://avatars.githubusercontent.com/u/1252021?v=3","gravatar_id":"","url":"https://api.github.com/users/teppokoivula","html_url":"https://github.com/teppokoivula","followers_url":"https://api.github.com/users/teppokoivula/followers","following_url":"https://api.github.com/users/teppokoivula/following{/other_user}","gists_url":"https://api.github.com/users/teppokoivula/gists{/gist_id}","starred_url":"https://api.github.com/users/teppokoivula/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/teppokoivula/subscriptions","organizations_url":"https://api.github.com/users/teppokoivula/orgs","repos_url":"https://api.github.com/users/teppokoivula/repos","events_url":"https://api.github.com/users/teppokoivula/events{/privacy}","received_events_url":"https://api.github.com/users/teppokoivula/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":0,"created_at":"2015-05-21T06:41:26Z","updated_at":"2015-05-21T06:41:26Z","closed_at":null,"body":"In most (might even say \"all\") cases I'd prefer to skip the template / page level cache if GET or POST params are present. Currently I have to make changes to caching settings if I add a new feature that requires either of these, naming all possible params specifically, and this gets worse if it's a site-wide feature.\r\n\r\nI'd really prefer the cache to go away (don't cache content, don't serve cached content) if said params are present -- current behaviour seems counterintuitive, to be honest -- but since that would be a pretty big change to how this works, a wildcard setting would be nice."}}