search

influencia0406 / oauth-signpost

Automatically exported from code.google.com/p/oauth-signpost
0 stars 0 forks source link

gzip support #9

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago 
Signpost should support gzip encoding by default (for more effective use of 
slow (cell) networks).

Original issue reported on code.google.com by s...@mojodna.net on 9 Jun 2009 at 12:48

GoogleCodeExporter commented 8 years ago 
Can you elaborate on that? Do you mean that gzipped message bodies should be 
unzipped
in order to account for parameters sent in the message payload?

Original comment by m.kaepp...@gmail.com on 13 Jun 2009 at 1:58

GoogleCodeExporter commented 8 years ago

Original comment by m.kaepp...@gmail.com on 18 Jun 2009 at 9:09

GoogleCodeExporter commented 8 years ago 
No, it should support gzip compression of the response (using the 
Content-Encoding header).  It's a way that 
websites are optimized (by reducing the amount of data that's transferred).  
HTTPClient supports it, but I don't 
remember it being straightforward.

Original comment by s...@mojodna.net on 6 Jul 2009 at 10:41

GoogleCodeExporter commented 8 years ago 
If we do a OAuthProvider.setRequestHeader("Accept-Encoding", "gzip, deflate"), 
the
library breaks if the service provider sends the data in gzip format. Basically 
you
will have to check if the HttpURLConnection.getContentEncoding() is "gzip", then
uncompress the input stream before processing. (like new
GZIPInputStream(conn.getInputStream()))

Not critical but it would be a nice to have.

Regards
Nabeel Mukhtar

Original comment by nabeelmukhtar on 12 Mar 2010 at 9:25

GoogleCodeExporter commented 8 years ago

Original comment by m.kaepp...@gmail.com on 14 Mar 2010 at 4:55