Thanks for the reply. But not every web page
needing to post
more than 2048 bytes of data
are dealing with purchasing. In fact, I would dare say, most web pages needing to post more than 2048 bytes of data are not dealing with purchasing.
I have learned some things. If I use document.write to rewrite the whole page, at the event of body.onload or document.onreadystatechange, the browser message
is killed. Example:
~~~~ Some ASP stuff ~~~~
var csBody = document.body.innerHTML;
document.style.display = "inline";
<body onload='OnLoad();' style="display: none;">
<form method=post action="Redirect-EXP.asp">
<input type=text name=STATE value="<%=csSTATE%>"><br>
<input type=submit value="Submit">
The interesting thing about this approach is that it completely kills the IE "resend info", and does not let F5/Refresh bother the server. This is great, not perfect, but along the lines of what I need.
It has these limitations.
1) To truly refresh EVER again, one will have to code
a button as even Control-F5 does not get any response
back to the server.
2) Styles/script, and absolute/relative positioned elements get messed up.
Has anyone pursued this corse of action against the "resend info" dialog?
Any ideas on making
absolute/relative positioning to behave properly again?
I also tried document.location.search = "" but this caused the web page to immediately post, and worse, it posted
with no form