On Fri, Feb 8, 2013 at 2:23 AM, Themba Fletcher <themba.fletc...@gmail.com>wrote:
> If I understand correctly the OPTIONS request is forced by the fact that > your POST's content-type is application/json > -- Any request that's not a Simple Request gets a preflight because the > W3C says so. Simple requests are defined as (emphasis mine): > > >> - Only uses GET or POST. If POST is used to send data to the server, >> the *Content-Type of the data sent to the server with the HTTP POST >> request is one of application/x-www-form-urlencoded, multipart/form-data, >> or text/plain.* >> >> Aha - i could just change it to text/plain - the JSON API is set up to accept that one. i'll try that out tonight. Thank you :) > >> >> >> - >> >> So I think "the resource" -- fossil in this case -- is going to have to > respond properly to a CORS preflight OPTIONS request. I started reading > through this http://www.w3.org/TR/cors/#resource-preflight-requests and > then my eyes began to bleed and I had to stop :) > Thank you for the link - i'll give it a read and let you know what happens (if my eyes don't bleed out, that is). -- ----- stephan beal http://wanderinghorse.net/home/stephan/ http://gplus.to/sgbeal
_______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
