I've been working on improving the speed of my application and noticed that when I turn off wifi and use the 3G connection, http requests no longer use http compression.
Specifically, when using the 3G connection, the "Accept-Encoding" header (which I have set to "gzip, deflate") are stripped off before the request arrives at my server. I tested this with the HttpClient class, and with my own custom http client through java.net.Socket. I then also verified this using the native android web browser. With wifi turned on, my server recieves a header "Accept-Encoding: gzip". With wifi turned off, and using the 3G connection, my server does not receive that header. I initially thought this might be an intentional behavior as part of 3G connections, but then I tested it with a 3G iphone (on AT&T), and there was no such problem there. So I'm guessing it's a problem specific to T-Mobile. i wonder if there is some proxy that is intentionally stripping out this header. I'd appreciate any advice about this. For an XML-based web service like mine where the response data has a high compression ratio, this behavior causes a significant speed hit. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -~----------~----~----~----~------~----~------~--~---
