Is it a great sin if a server implementation does something like this: GET /test/test.html returns Content-Type: text/html GET /test/test.html?type=xml return...
... Neither feel good to me, If a resource is HTML, then you should it's content-type should be HTML. If it's some XML other than XHTML or well-formed HTML...
... I probably should've stated more clearly in my original post: the body of response is indeed XHTML. I am trying to work around a very specific issue, which...
... HTML is only sometimes XML. If the HTML has one of the W3 DTDs it is likely that it is not XML compliant. Having said that, it is possible to produce...
here's some ideas to share.. In the _ideal_ REST world, a good resource identifier, URL should not contain representation-specified information, "Accept"...
... This is all very good advice. Remember though, that REST is *really* useful for webservices where HTML is not an issue. If you're designing a web...
I've noticed these cases are not the correct way to deal with content negotiation after started to read HTTP/1.1 spec in details yesterday. i'm now seeking for...
... Could you post the details of your research here? I am very interested in this topic, as well. ... The browsers don't, but the XMLHttpRequest allows that...
... i'm doing a study on practical REST implementation in current web application. IMHO, it might be a good start to introduce REST to public, by showing...
... In what way were the scenarios you outlined incorrect? ... I'd say Accept is the way to do it... but a browser is primarily an HTML rendering tool. I'm not...
... I'm still trying to study more details about content negotiation in HTTP/1.1 But as far as i know now, an appropriate way for server to handle Accept tag...
... that's the problem..when RESTie meets The Browser. :P Although REST encourage URL not to be representation-specific (ex. trailing .html, .xml, .atom etc) ...
... I think you're overestimating the role of the browser in REST. REST is a set of strictures for the creation of webservices. It's primary competitor is...
... The requirement for extensions is because of the interface with MIME helper apps. They're invoked by the browser with a single command-line parameter, the...
... AAAaaarrrggghhh!! Any time your understanding of REST disagrees with your understanding of how the Web works, one or the other is *wrong*. REST is all...
... I'm not sure if you mean this as a personal insult or as a general statement. If it's a personal insult then fine. But if it's a general statement then...
... Hi Nic! I didn't intend it as personal, but I realize it sounded that way and I apologize. It's a general frustration with many recurring discussions by...
... I do agree with you. My point is that human facing webapps (as opposed to machine facing ones which we might call web services) sometimes have to be a...
... No, there are three resources. One is your generic bank statement. Second is your bank statement in PDF. Third is your bank statement in HTML. Three...
... When you PUT the server could use the content-type to decide what representation is to be edited. I don't understand why you class that as gymnastics. ...
... Because I've written HTTP clients and HTTP servers. If the server assumes that every content type is a variant of a single resource instead of a...
... Yes. I know. And you wrote the specs. It's certainly difficult arguing with you because of that. But hey! I'm cantankerous! I have written clients and...