Not sure if there are any other references. I experienced the problem and googled on it. Like Mark wrote it seemed like some other people had the problem but they hadn't found a solution. The client side XSL transformations are, as far that I have understood it, supported by currently known browsers. So when the browser is presented with an XML file with a valid reference to a XSL transform side it will automatically transform it and present the (in most cases) resulting HTML.
But why the apache HTTPclient does it per default l can not understand. Oh, and I did try to ask http://hc.apache.org but surprise surprise.. no response :) I guess I can try to get hold of another 3rd party http client but it would be nice if I could use the build in. /M On 25 Apr, 21:36, Mike Hearn <[email protected]> wrote: > Is there a reference for that behavior? Can it really be true that an > HTTP library includes an XSL transformer? That's some serious scope > creep if so! --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to [email protected] 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 -~----------~----~----~----~------~----~------~--~---
