On Fri, Feb 8, 2013 at 2:23 AM, Themba Fletcher
themba.fletc...@gmail.comwrote:
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
On Fri, Feb 8, 2013 at 2:26 AM, Themba Fletcher
themba.fletc...@gmail.comwrote:
Whoops -- please ignore the previous stuff for now.
You have a doubled Access-Control-Allow-Origin header in your response:
i saw that but it's not my fault - if i don't configure Apache to send
this header then
I should clarify a bit Stephan -- it was not specifically a doubled
Access-Control-Allow-Origin header that destroyed my week but rather was a
doubled Content-Length header. I was in the same boat as you though. If I
explicitly added it it was doubled, and if not it wasn't correct (on that
server
Hi, all,
i am trying, as a proof-of-concept, to host a fossil repo using the new
Google Drive feature of being able to host HTML/JS/CSS (as a basis i'm
using an existing custom fossil UI built on the JSON API). It's _almost_
working but falls flat due to CORS (cross-origin calls) limitations and
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
5 matches
Mail list logo
