[stardotstar]

Originally Posted by zbosskiller

Hi,

I've had this mod installed for around 6 weeks. It worked great. Yesterday got home from work, haven't modified the site at all and the chat box says 'Loading' and also the same applies to the 'CYB Stats'

Any ideas would be really appreciated. It's obviously something to do the AJAX but can't figure it out.

Cyber, can you help me please?

Thx

Zboss

I concur: this plugin is hanging with "Loading..." and displays an error on page in MSIE (not Firefox) only as of a day or so ago??! I notice the same issues being reported by users of the advanced stats - anyone have this with cyb-chatbox?

This excellent chat has been working without issues for some time now - and I am using 2.3 - it is same behaviour on a board without advanced stats - so it is an implementation thing common to the two in MSIE...

TIA
\\'

Could it be related to these kinds of coding issues:

Originally Posted by http://devcentral.f5.com/weblogs/macvittie/archive/2008/06/26/3397.aspx

Most of the implementations also realize HTTP caching. Internet Explorer and Firefox do, but there is a difference in how and when the cached data is revalidated. Firefox revalidates the cached response every time the page is refreshed, issuing an "If-Modified-Since" header with value set to the value of the "Last-Modified" header of the cached response.

Internet Explorer does so only if the cached response is expired (i.e., after the date of received "Expires" header).

Basically, the problem lies with IE's caching mechanisms. So if you were trying to build an AJAX application with a real-time updating component and it didn't seem to work in IE, now you may know why that is.

There are workarounds:

1. Modify the AJAX call (within the client-side script) to check the response and, if necessary, make a second call with a Date value in the past to force the call to the server.
2. Append a unique query string to the call, for example appending a timestamp. This makes the URI unique, ensuring it won't be in the cache and forcing IE to call out to the server to get it.
3. Change all requests to use POST instead of GET.
4. Force the "Expires" header to be set in the past (much in the way we expire cookies programmatically). Setting cache control headers may also help force IE to act according to expectations.