Here's some more info: The problem seems to be related to having an immediate expiration on the web-page (HTTP-EQUIV Expires Content=0). But I NEED that functionality. It's crazy: Microsoft seems to have things set up so that when the web-page expires, the javascript in the Onload() won't run any more because its security context is no longer valid. Which means that no immediately-expiring web pages can have javascript in their onload() event.

>Help!!! I'm encountering many browser-side scripting errors that only happen with XP SP2. So far, the best I can replicate the problem is:
>- User clicks hyperlink like: page1.asp?p1=1#pageposn (note the page-relative anchor "pageposn"; this seems to be a key ingredient).
>- page1.asp does something, then it redirects to another page (exact same web site and virtual folder), such as page2.asp. Page2.asp generates the outbound html, and includes the expected anchor tag in the generated html for the anchor called "pageposn". FOR YEARS in the past, with every modern browser, this has worked. The browser scrolls down the delivered page to the anchor.
>- But now, any such pages with javascript in them will FAIL with an ACCESS DENIED error when browser-side javascript code tries to access any global javascript variables.
>- If you then click the refresh button (refreshing from page2.asp), the error condition does not happen.
>
>WTF?!!!!
>
>Has anybody else encountered such behavior? This is causing me major problems. Thanks for any help.