IsPostBack but in ASP

Seb

Hello,

Is there the IsPostBack command in ASP (not ASP.net) ?
Or How can I detect a refresh in a ASP page ?
Thanks

Sebastien

Oct 3 '07 #1

Follow Post Reply

8306

Anthony Jones

"Seb" <a@a.frwrote in message
news:47***********************@news.free.fr...

Hello,

Is there the IsPostBack command in ASP (not ASP.net) ?
Or How can I detect a refresh in a ASP page ?
Thanks

Sebastien

Function IsPostBack()
IsPostBack = (Request.ServerVariables("REQUEST_METHOD") = "POST")
End Function

--
Anthony Jones - MVP ASP/ASP.NET

Oct 4 '07 #2

=?Utf-8?B?U2Vi?=

Hello

Sorry but it's good to detect a POST but not to detect a refresh.

Thanks

Sebastien

"Anthony Jones" wrote:

"Seb" <a@a.frwrote in message
news:47***********************@news.free.fr...
Hello,

Is there the IsPostBack command in ASP (not ASP.net) ?
Or How can I detect a refresh in a ASP page ?
Thanks

Sebastien

Function IsPostBack()
IsPostBack = (Request.ServerVariables("REQUEST_METHOD") = "POST")
End Function

--
Anthony Jones - MVP ASP/ASP.NET

Oct 4 '07 #3

McKirahan

"Seb" <a@a.frwrote in message
news:47***********************@news.free.fr...

Hello,

Is there the IsPostBack command in ASP (not ASP.net) ?
Or How can I detect a refresh in a ASP page ?

Will something lke this work for you?

It uses Session variables to identify the current page
and its counter.

Create "refresh1.asp" then copy it to "refresh2.asp"
and change the value of "cASP" to "refresh2.asp".

Call it via http://{your domain}/refresh1.asp then
click the links and watch the page+counter display.
Clicking "Refresh" will increment the counter as well.

<%@ Language="VBScript" %>
<% Option Explicit
Const cASP = "refresh1.asp"
If Session("ASP") <cASP _
Or Session("CTR") = "" Then
Session("CTR") = 0
Else
Session("CTR") = Session("CTR") + 1
End If
Session("ASP") = cASP
%>
<html>
<body>
<%=Session("ASP")%: <%=Session("CTR")%>
<hr>
<a href="refresh1.asp">1</a| <a href="refresh2.asp">2</a>
</body>
</html>

Oct 4 '07 #4

Bob Barrows [MVP]

?
Not even .Net's IsPostBack method can distinguish between an initial
page request and a subsequent page refresh ...

To do that, you will probably need to use a session variable to track
when the page is initially requested

Seb wrote:

Hello

Sorry but it's good to detect a POST but not to detect a refresh.

Thanks

Sebastien

"Anthony Jones" wrote:

>"Seb" <a@a.frwrote in message
news:47***********************@news.free.fr...
>>Hello,

Is there the IsPostBack command in ASP (not ASP.net) ?
Or How can I detect a refresh in a ASP page ?
Thanks

Sebastien

Function IsPostBack()
IsPostBack = (Request.ServerVariables("REQUEST_METHOD") = "POST")
End Function

--
Anthony Jones - MVP ASP/ASP.NET

--
Microsoft MVP -- ASP/ASP.NET
Please reply to the newsgroup. The email account listed in my From
header is my spam trap, so I don't check it very often. You will get a
quicker response by posting to the newsgroup.

Oct 4 '07 #5

Anthony Jones

"Seb" <Se*@discussions.microsoft.comwrote in message
news:F6**********************************@microsof t.com...

Hello

Sorry but it's good to detect a POST but not to detect a refresh.

Thanks

Sebastien

I see. Most refreshes are accompanied with a pragma: no-cache header but
that isn't guaranteed nor is it guaranteed that the initial request will not
be accompanied by the header.

The best way to ensure you don't reprocess the same post is to add a hidden
field containing a unique ID (such as a GUID) to the form.

When you've processed the POST of the form make a record of the UniqueID to
mark that its been processed. Before processing a POST check that you
haven't got a record of that POST already.

--
Anthony Jones - MVP ASP/ASP.NET

Oct 4 '07 #6

=?Utf-8?B?U2Vi?=

Thank you everybody

Finally I have used a Session variable to save the last post but it's not a
unique ID because my unique ID is calculated when I have a new post.

By
SÃ©bastien
"Anthony Jones" wrote:

"Seb" <Se*@discussions.microsoft.comwrote in message
news:F6**********************************@microsof t.com...
Hello

Sorry but it's good to detect a POST but not to detect a refresh.

Thanks

Sebastien

I see. Most refreshes are accompanied with a pragma: no-cache header but
that isn't guaranteed nor is it guaranteed that the initial request will not
be accompanied by the header.

The best way to ensure you don't reprocess the same post is to add a hidden
field containing a unique ID (such as a GUID) to the form.

When you've processed the POST of the form make a record of the UniqueID to
mark that its been processed. Before processing a POST check that you
haven't got a record of that POST already.

--
Anthony Jones - MVP ASP/ASP.NET

Oct 5 '07 #7

This discussion thread is closed

Similar topics