That very well could be a bug in the chunk encoding support of the http rewriter within the emulator's proxy code. I could not test it against a lot of cases.
Can you dump the output of "emulator -debug-proxy" when you try to connect to www.google.com through your proxy ? This will print out the exact messages exchanged. On Tue, Mar 24, 2009 at 3:39 PM, m5p3nc3r <matt...@thespencers.me.uk> wrote: > > Hi All > > I am having a specific problem that is preventing me using the android > SDK from work. We are using a MS Proxy here that all internet traffic > has to go through. The problem seems to be when the emulator is > trying to access a site that uses 'Transfer-Encoding: chunked' > > If I attempt to download www.nds.com (no chunked encoding) into the > browser, it works fine. > > However if I try to go to www.google.com (uses chunked encoding), the > browser fails with the message: > can't determine content length, and client wants to keep connection > opened > > My feeling (and I'm no expert in this area) is that the underlying > code managing the communication through the proxy is not dealing with > the null terminator on the chunk encoded response when the connection > to the proxy is being kept open? > > Does anyone have any experience in this area? Is the source to the > emulator available so I can try and understand what is going on here? > > Cheers > > Matt > > > --~--~---------~--~----~------------~-------~--~----~ 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 android-developers-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -~----------~----~----~----~------~----~------~--~---
