There are currently two versions of the request content-type floating around the Shindig java code, one in the RemoteContentRequest.contentType variable and another in the RemoteContentRequest.headers variable. Values can make their way into the content type through several mechanisms, including javascript running on the client and hardcoded values in the Shindig code.
I'm sure there is some corollary to Murphy's Law that says that if you have two versions of a piece of data floating around, one will be wrong. I'd like to fix RemoteContentRequest so that there is a single location that someone can check to see what content-type header was specified by gadgets.io.makeRequest. Does anyone feel strongly about where that single location should be, or should I just pick one? Cheers, Brian
