5 ms·
A large part of the reason that many APIs fail at content negotiation has to do with the fact that many clients don't support it properly. Chrome in particular
by T-R 14y ago
A large part of the reason that many APIs fail at content negotiation has to do with the fact that many clients don't support it properly. Chrome in particular completely ignores the Vary header (and its devs have marked the issue as "won't fix"), so it's not practical to have the same URL respond with different media types based on the Accepts header (it overwrites the cached item, so the back button doesn't work properly). Many APIs compensate for this by putting the format in a query parameter.
- alistair77 14y agoGood news is that this will be fixed in Chrome v25 (http://code.google.com/p/chromium/issues/detail?id=94369 http://code.google.com/p/chromium/issues/detail?id=94369). Recent versions of Firefox and IE already provide good support.
- T-R 14y agoThat's great to hear. Thanks for the heads up.