Hey, all, Just wanted to confirm this issue -- I tried hitting widget.js both with Firefox's default Accept-Encoding request header of "gzip,deflate" and with Accept-Encoding overridden to just "gzip" -- in both cases, the returned response was not compressed (tested on FF 3.6.17, using the LiveHTTPHeaders plug-in to view request and response headers).
It is kinda surprising, as you have to go all the way back to IE 4 or Netscape to find browsers that can't handle gzip. While 20k doesn't sound like so much by itself, on a user-facing piece of JavaScript for a company whose widgets are on a non-trivial fraction of web pages on the internet, that's a lot of users who could be seeing faster downloads, and a lot of bandwidth Twitter is paying for which they probably don't need to be. My $0.02, -Alex On Fri, May 20, 2011 at 8:37 AM, cfalar <carolfalard...@hotmail.com> wrote: > Hi, > I saw that the file http://widgets.twimg.com/j/2/widget.js is not > gzip. > It's can save about 20KB. > You can try this gzip test page with the file : > http://www.gidnetwork.com/tools/gzip-test.php > > Can you take a look at it? > > Thank you > > -- > Twitter developer documentation and resources: https://dev.twitter.com/doc > API updates via Twitter: https://twitter.com/twitterapi > Issues/Enhancements Tracker: > https://code.google.com/p/twitter-api/issues/list > Change your membership to this group: > https://groups.google.com/forum/#!forum/twitter-development-talk > -- Alex Feinberg CTO, Trak.ly http://trak.ly/ -- Twitter developer documentation and resources: https://dev.twitter.com/doc API updates via Twitter: https://twitter.com/twitterapi Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list Change your membership to this group: https://groups.google.com/forum/#!forum/twitter-development-talk
