{"html_url": "https://github.com/simonw/datasette/issues/1143#issuecomment-744618787", "issue_url": "https://api.github.com/repos/simonw/datasette/issues/1143", "id": 744618787, "node_id": "MDEyOklzc3VlQ29tbWVudDc0NDYxODc4Nw==", "user": {"value": 114388, "label": "yurivish"}, "created_at": "2020-12-14T18:15:00Z", "updated_at": "2020-12-15T02:21:53Z", "author_association": "NONE", "body": "From a quick look at the README, it does seem to do everything I need, thanks!\r\n\r\nI think the argument for inclusion in core is to lower the chances of unwanted data access. A local server can be accessed by anybody who can make an HTTP request to your computer regardless of CORS rules, but the default `*` rule additionally opens up access to the local instance to any website you visit while it is running. \r\n\r\nThat's probably not what people typically intend, particularly when the data is of a sensitive nature. A default of requiring the user to specify the origin (allowing `*` but encouraging a narrower scope) would solve this problem entirely, I think.\r\n\r\n\r\n", "reactions": "{\"total_count\": 0, \"+1\": 0, \"-1\": 0, \"laugh\": 0, \"hooray\": 0, \"confused\": 0, \"heart\": 0, \"rocket\": 0, \"eyes\": 0}", "issue": {"value": 764059235, "label": "More flexible CORS support in core, to encourage good security practices"}, "performed_via_github_app": null}