We don't support the X-Accept-Encoding header and there are no plans for it to be added to the API. I'm not familiar with the roadmap for Silverlight/Windows Phone development but suggest they are the best place to ask about unlocking the ability to set those headers.
Best @themattharris Developer Advocate, Twitter http://twitter.com/themattharris On Mon, Jan 24, 2011 at 2:28 PM, David W <d_wy...@yahoo.com> wrote: > In Silverlight (and thus Windows Phone development) a developer is not > allowed, for reasons unknown to me, to edit or alter the Accept- > Encoding HTTP header. More info here: > > http://msdn.microsoft.com/en-us/library/system.net.webheadercollection%28v=VS.95%29.aspx > > As such it's not possible to add gzip to the Accept-Encoding header > and get a compressed response. > > I've seen other server-side implementations provide a work around to > this by also checking a custom HTTP header for Accept-Encoding values, > such as X-Accept-Encoding. > > Is this something that Twitter does, I'm guessing the answer is no, > but thought I'd ask otherwise Silverlight and Windows Phone dev's > won't be able to request gzip'd requests. > > Thanks, > dw. > > -- > Twitter developer documentation and resources: http://dev.twitter.com/doc > API updates via Twitter: http://twitter.com/twitterapi > Issues/Enhancements Tracker: > http://code.google.com/p/twitter-api/issues/list > Change your membership to this group: > http://groups.google.com/group/twitter-development-talk > -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk