Amos: in the example i attached: X-Accept-Types: text/html,text/xml,application/json is what clients can use when negotiating responses from servers X-Content-Types: text/xml,application/x-www-form-urlencoded,application/json is what clients can use when constructing bodies that will be sent to servers There might be better names for these two cases. mca http://amundsen.com/blog/ http://twitter.com@mamund http://mamund.com/foaf.rdf#me On Mon, Dec 12, 2011 at 23:19, Amos Jeffries <squid3@treenet.co.nz> wrote: > On 13/12/2011 10:56 a.m., mike amundsen wrote: >> >> Yes, I think this could be helpful. >> >> I adopted a similar pattern for some internal work a while back that >> addressed this problem[1]: >> >> In a nutshell, I added this to options: >> >> -- Typical call to OPTIONS for this URL >> REQUEST: ************** >> OPTIONS /xcs/ugdata/ HTTP/1.1 >> content-type:text/plain >> Host: localhost >> Accept: */* >> >> RESPONSE: ************** >> HTTP/1.1 200 OK >> Allow: DELETE,GET,HEAD,OPTIONS,POST,PUT >> X-Accept-Types: text/html,text/xml,application/json >> X-Content-Types: >> text/xml,application/x-www-form-urlencoded,application/json > > > You seem to have a problem: the two headers are advertising two unique sets > of mime types as being accepted from the client by this server. > Surely it should at least be advertising a consistent set. > > AYJ > >Received on Tuesday, 13 December 2011 04:27:36 UTC
This archive was generated by hypermail 2.4.0 : Thursday, 2 February 2023 18:43:26 UTC