You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@wicket.apache.org by hillj2 <Hi...@michigan.gov> on 2007/09/04 15:40:38 UTC

Re: wicket-event.js returning unreadable

I believe I've finally solved my problem.

No doubt the original problem was double compression resulting from using a
homegrown compression filter on top of wicket's default compression.  After
being forced to look at this issue again, which suddenly seemed to not only
be a problem with just IE (FF suddenly seemed to work fine) but only with
the IE on MY computer, I ended up clearing IE's temporary internet files. 
Problem solved.  So IE cached the double compressed version of the js file
and kept it in cache for several weeks until I manually deleted it.

For now it's looking like the problem is solved.  (Thanks, Microsoft, for
introducing the world to permanent temporary internet files.)

Joel
-- 
View this message in context: http://www.nabble.com/wicket-event.js-returning-unreadable-tf4158501.html#a12478274
Sent from the Wicket - User mailing list archive at Nabble.com.


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org