even if an user choose to add a suffix (html/json) to a page name, if an accept header is defined then the suffix is ignored. The default behaviour for a web browser is to send an accept header misunderstood by the current code, so user will always retrieve json data when he asked for html ou other.
[x] Manage default Accept header value from common browsers
[x] Accept header supersedes suffix if both are sent by client
[x] json format remains the default
[x] unsupported formats brings a NotAcceptable error when a GET request is sent on collection items(/collections/{collection}/items) or a specific item /collections/{collection}/items/{fid}
even if an user choose to add a suffix (html/json) to a page name, if an accept header is defined then the suffix is ignored. The default behaviour for a web browser is to send an accept header misunderstood by the current code, so user will always retrieve json data when he asked for html ou other.
See also #41