I have an issue ( ) related to Ajax responses and GZIP compression. This is in the context of the Apache Tapestry web framework, which uses Prototype & Scriptaculous.
The issue is that if the response to an Ajax response is compressed with GZIP, some users see problems: the content visible to the client web browser is garbled. I haven't seen this, but I tend to test my apps direct (browser directly to servlet container, nothing in the middle). My working theory is that a firewall (or proxy) between the browser and the servlet container is at fault. Tapestry does the right thing, in terms of settitng the Content-Encoding header to "gzip" when it is sending a compressed stream. Apparently, this only happens for application/json responses, not for text/javascript responses. Is anyone aware of similar problems in their apps? I'd prefer not to disable compression of application/json responses. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Prototype & script.aculo.us" 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/prototype-scriptaculous?hl=en -~----------~----~----~----~------~----~------~--~---
