- From: Markus Lanthaler <markus.lanthaler@gmx.net>
- Date: Mon, 4 Aug 2014 21:41:30 +0200
- To: <public-hydra@w3.org>
On 1 Aug 2014 at 22:58, Kuno Woudt wrote: > Hello, > > On 31-07-14 23:54, Markus Lanthaler wrote: >> On 1 Aug 2014 at 00:57, Gregg Kellogg wrote: >> >>> Not useful if you're using your API also as a website; A web browser >>> won't act too kindly to a 404 response, even with a body, AFAIK. >> If a body is returned, a browser will display it exactly the same way as if >> the status code were 200. > > Internet Explorer in some rare situations doesn't display the response > body, which may be what Gregg was referring to: > > http://stackoverflow.com/questions/16741062/what-rules-does-ie-use-to-det > ermine-whether- to-show-the-entity-body > > Remember to pad your error responses :) Thanks for digging this out Kuno. Very interesting and a nice example of what things happen in a distributed system that hasn't been designed and run by a central authority. Don't forget to read the blog post from IE's engineering team [1] which explains the why. [1] http://blogs.msdn.com/b/ieinternals/archive/2010/08/19/http-error-pages-in-i nternet-explorer.aspx -- Markus Lanthaler @markuslanthaler
Received on Monday, 4 August 2014 19:42:03 UTC