G
Gianluca Maggio
Hi,
I have the same problem with response redirect but not on every page of our
application that use redirection, only in one situation that is too complex
to analyze.
So I tried to reproduce the error with a simple couple of test page, but
with a simple page redirection like <% response.redirect URL%> doesn't show
the error.
I tried with a lot of combinations but nothing to do... the error can't be
reproduced.
Finally I tried to put in my URL an anchor reference and, combined with
<meta http-equiv="Content-Type" content="text/html; charset=utf-8"> now I
have the error.
I think that there are a lot of situation in which IE6 with Sp2 thinks
(making a mistake) that there are security problems and for this lock out
the access to the object model. This is too bad!
This my test code. (Note. Remove #N1 in the url or <meta ...> and the error
disappear.)
default.asp
------
<%
Response.Redirect "test.asp?Foo=Y#N1"
%>
------
test.asp
------
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<title>Line</title>
</head>
<body onload="alert(document.location);">
<p>Line</p><p>Line</p><p>Line</p><hr>
<p>Line</p><p>Line</p><p>Line</p><hr>
<p>Line</p><p>Line</p><p>Line</p><hr>
<p>Line</p><p>Line</p><p>Line</p><hr>
<p>Line</p><p>Line</p><p>Line</p><hr>
<p>Line</p><p>Line</p><p>Line</p><hr>
<p><a name="N1">Bookmark</a></p><p>Line</p><p>Line</p><hr>
</body>
</html>
I have the same problem with response redirect but not on every page of our
application that use redirection, only in one situation that is too complex
to analyze.
So I tried to reproduce the error with a simple couple of test page, but
with a simple page redirection like <% response.redirect URL%> doesn't show
the error.
I tried with a lot of combinations but nothing to do... the error can't be
reproduced.
Finally I tried to put in my URL an anchor reference and, combined with
<meta http-equiv="Content-Type" content="text/html; charset=utf-8"> now I
have the error.
I think that there are a lot of situation in which IE6 with Sp2 thinks
(making a mistake) that there are security problems and for this lock out
the access to the object model. This is too bad!
This my test code. (Note. Remove #N1 in the url or <meta ...> and the error
disappear.)
default.asp
------
<%
Response.Redirect "test.asp?Foo=Y#N1"
%>
------
test.asp
------
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<title>Line</title>
</head>
<body onload="alert(document.location);">
<p>Line</p><p>Line</p><p>Line</p><hr>
<p>Line</p><p>Line</p><p>Line</p><hr>
<p>Line</p><p>Line</p><p>Line</p><hr>
<p>Line</p><p>Line</p><p>Line</p><hr>
<p>Line</p><p>Line</p><p>Line</p><hr>
<p>Line</p><p>Line</p><p>Line</p><hr>
<p><a name="N1">Bookmark</a></p><p>Line</p><p>Line</p><hr>
</body>
</html>