Martin, I think we found a culprit. There are some http 504 errors appearing eventually in the transparent proxy that we set up. I think at this point it is a networking issue.
Many thanks for responding. Sincerely, Dawid On Thu, Dec 29, 2011 at 9:33 AM, Dawid Dudzinski <[email protected]> wrote: > Wicket 1.4.15 > Images are img tags returned through Wicket's AjaxRequestTarget > object. The app returns new markup that is supposed to get rendered in > browser. > > So far all indications are that the html is generated properly - we > used a transparent proxy between browser and server to inspect > requests and responses. > > We also uncovered an issue with failed HTTP 302 redirects. It is a > possibility that this is causing the problem. > > In the meantime are you aware of any relevant issues that had been > addressed in subsequent Wicket releases? > > Thanks, > Dawid > > > > On Thu, Dec 29, 2011 at 12:23 AM, Martin Grigorov <[email protected]> > wrote: >> Which version of Wicket ? >> What kind of request loads the image - Ajax or normal ? >> >> On Thu, Dec 29, 2011 at 4:47 AM, Dawid Dudzinski <[email protected]> wrote: >>> Hello, >>> >>> I have an issue that may not be related to Wicket but I'm trying every >>> possible angle to solve my issue quickly and any suggestion would be >>> greatly appreciated. >>> >>> I have an application that for the most part loads only one screen and >>> then swaps out data via Wicket calls. It runs about 10-12 hours a day >>> non-stop and from time to time my users run into a situation where >>> images just stop loading in IE6. The only fix at that point is to >>> clear browser cache and things come back to normal. It may be worth to >>> mention that part of the functionality is an image browser. >>> >>> Image implementation extends the NonCachingImage class but 99% of the >>> time user will works with unique images. >>> >>> Like I wrote above, the application just stops loading images and >>> users have to clear the browser cache to get the app running again. >>> >>> I can't test it with newer browsers - not even newer IE and it only >>> happens after an extended usage. >>> >>> Has anyone run into the same or similar issue? If anyone had to >>> venture a guess it it could be related to Wicket in any way? >>> >>> Thanks in advance, >>> Dawid >>> >>> --------------------------------------------------------------------- >>> To unsubscribe, e-mail: [email protected] >>> For additional commands, e-mail: [email protected] >>> >> >> >> >> -- >> Martin Grigorov >> jWeekend >> Training, Consulting, Development >> http://jWeekend.com >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [email protected] >> For additional commands, e-mail: [email protected] >> --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
