UTF8 suffix to content type confuses Piston
Maybe it's FF3.5, maybe it's jQuery, or maybe it's something to do with the page the post is coming from... anyway, my AJAX POST requests contain:
And, in utils.py, Piston is looking for exact match of:
Suffice to say, neither the twain shall meet, and my API explodes, having not found a suitable loadee in the translate() function.
Could this be better as a partial match?