AFAIK the content_type is for the content type you expect, not for the content type you are sending to the server.
On Wed, Sep 8, 2010 at 1:11 PM, Eric Woods <[email protected]> wrote: > Hey guys, > > We are seeing an issue while using the gadgets.io.makeRequest API in which > the specified Content-Type is not used in the final request that Shindig > forwards to the recipient. For example: > > var params = {}; > params[gadgets.io.RequestParameters.CONTENT_TYPE] = > gadgets.io.ContentType.TEXT; > gadgets.io.makeRequest(url, callback, params); > > The Content-Type that is ultimately used in the actual request header (as > verified in Firebug) is always "application/x-www-form-urlencoded; > charset=UTF-8". > > As a workaround, we've discovered that the following snippet works: > var params = {}; > var headers = > { > "Cache-Control": "no-cache, must-revalidate, post-check=0, > pre-check=0", > "content-type":" "application/atom+xml;type=entry", > "Expires": 0, > "Pragma": "no-cache" > } > > Note that we are seeing this issue in the 2.0.x build of Shindig (I haven't > verified it on the latest trunk). Is this an issue to raise in JIRA? > > Thanks, > Eric W. > -- Jacobo Tarrío | http://jacobo.tarrio.org/
