I see that you resolved the problem, but will throw in a last two cents... At least in my case, the site would work internally when there was a file date problem, too--but I think the difference is that we did have caching on. I also (now) remember having this problem another time, where there was a different problem. Disabling caching exposed the problem as a bad cache, which I then deleted. IIRC, restarting the service/server didn't help in that case. Bill Mayo ________________________________ From: isalist-bounce@xxxxxxxxxxxxx [mailto:isalist-bounce@xxxxxxxxxxxxx] On Behalf Of Thor (Hammer of God) Sent: Thursday, January 10, 2008 6:48 PM To: isalist@xxxxxxxxxxxxx Subject: [isalist] Re: Changes in web site not reflecting Yes, the new file has the correct date/time stamp. As I said, it works internally, just not through ISA... Tried the Ctrl-F5 trick, and that doesn't work. This is happened before, and I'm not sure what I did to fix it (other than maybe rebooting). Any other ideas? This is quite strange... t From: isalist-bounce@xxxxxxxxxxxxx [mailto:isalist-bounce@xxxxxxxxxxxxx] On Behalf Of Mayo, Bill Sent: Thursday, January 10, 2008 1:41 PM To: isalist@xxxxxxxxxxxxx Subject: [isalist] Re: Changes in web site not reflecting I have seen this happen where the updated files on the internal site actually have an older date than the ones they replaced. The solution for this is to "touch" the files to update the modification date. Bill Mayo ________________________________ From: isalist-bounce@xxxxxxxxxxxxx [mailto:isalist-bounce@xxxxxxxxxxxxx] On Behalf Of Thor (Hammer of God) Sent: Thursday, January 10, 2008 3:48 PM To: isalist@xxxxxxxxxxxxx Subject: [isalist] Changes in web site not reflecting OK, we and an un-named Scot can't figga this one out. Typical web publishing rule - everything works fine. However, if I change content on the internal server, when you view the site externally (via ISA) the "old" content is still there like it's cached or something. Viewing the site internally shows the new content. Even disabling and re-enabling the rule exhibits the same behavior (disabling the pub rule prevents access to the site as expected). The site is exempt from ISA caching rules. The internal server has been rebooted, etc (which you would not have to do, but just letting you know). WTF is going on here? What have I forgotten? t