Embed Notice

@simon so, I can see it being useful when a resource can be retrieved with a explicit type, like

GET /resource.json

or

GET /resource?format=json

...and when you instead do

GET /resource

...it tries to guess the best format for you.

But I agree that it's a little disconcerting when you test the API in a browser, and then shift to a standard library for a scripting language that has different header defaults.