payload: {"action":"opened","issue":{"url":"https://api.github.com/repos/plone/plone.rest/issues/87","repository_url":"https://api.github.com/repos/plone/plone.rest","labels_url":"https://api.github.com/repos/plone/plone.rest/issues/87/labels{/name}","comments_url":"https://api.github.com/repos/plone/plone.rest/issues/87/comments","events_url":"https://api.github.com/repos/plone/plone.rest/issues/87/events","html_url":"https://github.com/plone/plone.rest/issues/87","id":423039351,"node_id":"MDU6SXNzdWU0MjMwMzkzNTE=","number":87,"title":"plone.rest should consider all calls to /api to be REST calls","user":{"login":"tisto","id":632105,"node_id":"MDQ6VXNlcjYzMjEwNQ==","avatar_url":"https://avatars0.githubusercontent.com/u/632105?v=4","gravatar_id":"","url":"https://api.github.com/users/tisto","html_url":"https://github.com/tisto","followers_url":"https://api.github.com/users/tisto/followers","following_url":"https://api.github.com/users/tisto/following{/other_user}","gists_url":"https://api.github.com/users/tisto/gists{/gist_id}","starred_url":"https://api.github.com/users/tisto/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/tisto/subscriptions","organizations_url":"https://api.github.com/users/tisto/orgs","repos_url":"https://api.github.com/users/tisto/repos","events_url":"https://api.github.com/users/tisto/events{/privacy}","received_events_url":"https://api.github.com/users/tisto/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":0,"created_at":"2019-03-20T02:41:33Z","updated_at":"2019-03-20T02:41:33Z","closed_at":null,"author_association":"MEMBER","body":"Using content negotiation in REST APIs is considered to be the correct way of doing things in sync with the HTTP specification. Though, in real life, there are some downsides to this approach:\r\n\r\n- Debugging and dev approachability: The dev always has to copy a CURL command to reproduce a REST call. Dev tools make things a lot easier but there is still a barrier and it confuses unexperienced devs\r\n\r\n- Cache poisoning: Turns our cache servers do not consider the content-type HTTP header and treat JSON and HTML documents as the same\r\n\r\nThe idea would be that we add an additional traversal hook that considers all calls that start with \"/api\" as plone.rest calls. The existing content-negotiation should stay in place for backwards compatibility and option if people want to use it."}}
other: {"actor":{"display_login":"tisto"}}