[ckan-dev] CORS problem

[William Waites]

If I had to guess, I would say it might have something to do with the
default content-type header which is probably multipart form encoded
or some such and when you try to parse the raw json as multipart it
fails. Or perhaps the reverse.

I also know from previous experience that pylons does some really
brain damaged things sometimes. For example. The openbiblio code (used
to) allow uploading a graph using PUT or POST. This data was
serialised as some kind of RDF as was reflected in the content-type
header.

Now if anything in the controller touched (i.e. even just to read) the
GET or POST request variables before you read the body, the body would
get re-encoded by pylons with all sorts of bogus % escapes and
such. This was a real pain to debug.

Not sure that's what's going on here though...

I'm around in IRC if you want to chat.

-w

* [2011-06-29 12:46:00 +0200] David Read <david.read at okfn.org> écrit:

] Will,
] 
] Do you have any idea about this header issue?
] http://trac.ckan.org/ticket/1206
] 
] BTW, I added 'Content-Type' to the allowable headers in the apache
] config on us7/test.ckan.net.
] 
] Andrea Fiore is here in Berlin working on ckanjs and could use some
] help on this today, if you're around.
] 
] David
] 
] _______________________________________________
] ckan-dev mailing list
] ckan-dev at lists.okfn.org
] http://lists.okfn.org/mailman/listinfo/ckan-dev

-- 
William Waites                <mailto:ww at styx.org>
http://river.styx.org/ww/        <sip:ww at styx.org>
F4B3 39BF E775 CF42 0BAB  3DF0 BE40 A6DF B06F FD45