Graham Parks wrote:
David Powell wrote:
Possibly, but that solution isn't perfect. There is a tradeoff between
supplying an inaccurate type, and supplying no type at all. This TAG
finding [1] discusses the issue quite thoroughly.
[1] http://www.w3.org/2001/tag/doc/mime-respect-20040225
Thanks for the pointer. Very useful.
The recommendation at the end of section 4.1 seems appropriate though.
If the advisory type attribute is incompatible, the client should query
the resource to double check, or at least offer the user the option of
double checking and/or loading the resource anyway.
Yes, this suggests that labeling the negotiated resource with one
specific media type *may* work, as long as the server falls back onto it
as a default (as opposed to sending a "300 Multiple Choices" response):
<content type="image/png" src="http://www.example.com/img"; />
But since my application currently does respond with "300 Multiple
Choices", I guess that I am stuck with violating the SHOULD and using
the following:
<content src="http://www.example.com/img"; />
Or is there any better way to handle this, given that 300 responses are
used?
At any rate, thank you all for your replies.
Regards,
Andreas Sewe
