{"action":"created","issue":{"url":"https://api.github.com/repos/algolia/places/issues/253","repository_url":"https://api.github.com/repos/algolia/places","labels_url":"https://api.github.com/repos/algolia/places/issues/253/labels{/name}","comments_url":"https://api.github.com/repos/algolia/places/issues/253/comments","events_url":"https://api.github.com/repos/algolia/places/issues/253/events","html_url":"https://github.com/algolia/places/issues/253","id":161867979,"number":253,"title":"Address autocompletion query should use GET and not POST","user":{"login":"patrickallaert","id":195277,"avatar_url":"https://avatars.githubusercontent.com/u/195277?v=3","gravatar_id":"","url":"https://api.github.com/users/patrickallaert","html_url":"https://github.com/patrickallaert","followers_url":"https://api.github.com/users/patrickallaert/followers","following_url":"https://api.github.com/users/patrickallaert/following{/other_user}","gists_url":"https://api.github.com/users/patrickallaert/gists{/gist_id}","starred_url":"https://api.github.com/users/patrickallaert/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/patrickallaert/subscriptions","organizations_url":"https://api.github.com/users/patrickallaert/orgs","repos_url":"https://api.github.com/users/patrickallaert/repos","events_url":"https://api.github.com/users/patrickallaert/events{/privacy}","received_events_url":"https://api.github.com/users/patrickallaert/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":1,"created_at":"2016-06-23T08:33:37Z","updated_at":"2016-06-23T09:51:41Z","closed_at":null,"body":"Shouldn't autocompletion queries use `GET` instead of `POST`? That would (e.g.) permit browser and reverse proxy cache."},"comment":{"url":"https://api.github.com/repos/algolia/places/issues/comments/228002859","html_url":"https://github.com/algolia/places/issues/253#issuecomment-228002859","issue_url":"https://api.github.com/repos/algolia/places/issues/253","id":228002859,"user":{"login":"vvo","id":123822,"avatar_url":"https://avatars.githubusercontent.com/u/123822?v=3","gravatar_id":"","url":"https://api.github.com/users/vvo","html_url":"https://github.com/vvo","followers_url":"https://api.github.com/users/vvo/followers","following_url":"https://api.github.com/users/vvo/following{/other_user}","gists_url":"https://api.github.com/users/vvo/gists{/gist_id}","starred_url":"https://api.github.com/users/vvo/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/vvo/subscriptions","organizations_url":"https://api.github.com/users/vvo/orgs","repos_url":"https://api.github.com/users/vvo/repos","events_url":"https://api.github.com/users/vvo/events{/privacy}","received_events_url":"https://api.github.com/users/vvo/received_events","type":"User","site_admin":false},"created_at":"2016-06-23T09:51:41Z","updated_at":"2016-06-23T09:51:41Z","body":"Hi Patrick, using POST or GET we could implement HTTP caching (https://www.mnot.net/blog/2012/09/24/caching_POST) but ultimately caching Algolia Places requests so CDNS or reverse proxy cache can cache them will be challenging.\r\n\r\nThe cache key would look something like $algolia_parameters-user_geolocation-user_ip. This is all we use to send relevant results to you.\r\n\r\nThus if we were to implement HTTP caching, there is a good chance we would have a lot of cache MISSes.\r\n\r\nRight now, we have a layer of caching inside the JavaScript code that is doing the work so that when you type \"a BACKSPACE a\" we only do one request.\r\n\r\nSo we have some caching, but at the user side, not HTTP wise.\r\n\r\nWhat do you think?"}}
{"actor":{"display_login":"vvo"}}