Yes, we already have gzip enabled. But the point isn't that the firewall blocks it - that's easy to solve - it's that we can't intercept the error and let the user know what to do. The simple way is we can tell them to login via https (which the firewall can't block). But we can't do that if we don't know there's a problem.
On Aug 13, 2:28 pm, Jeff Chimene <jchim...@gmail.com> wrote: > On 08/12/2009 07:24 PM, Joe Cole wrote: > > > > > > > I know it's a firewall because if we type the *.cache.html url into > > the browser it comes back with a document with a message from their > > firewall claiming it's been blocked. The file scored very highly on > > some metrics which their firewall uses. I am guessing it's because of > > the large js because it was the same in pretty mode. > > > We have seen this at two separate sites (different countries too), but > > with different builds of the software (we have different servers > > depending on the country). > > > Regardless, if there is a problem I'd love to be able to check (e.g. > > if the html downloaded by the nocache.js doesnt contain our script). I > > think this is something gwt should do out of the box really - because > > there are no errors thrown. Unfortunately the sites are private so I > > can't share the links. > > I don't have the links at hand, but have you tried enabling compression > on the server side? > > I think there may be some Apache incantations on this list to enable > that feature. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To post to this group, send email to Google-Web-Toolkit@googlegroups.com To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/Google-Web-Toolkit?hl=en -~----------~----~----~----~------~----~------~--~---
