- From: Amos Jeffries <squid3@treenet.co.nz>
- Date: Tue, 13 Dec 2011 17:19:25 +1300
- To: ietf-http-wg@w3.org
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:20:08 UTC