Account Options

  1. Sign in
The old Google Groups will be going away soon, but your browser is incompatible with the new version.
Google Groups Home
« Groups Home
Message from discussion CGI.pm: controlling Back & Reload
The group you are posting to is a Usenet group. Messages posted to this group will make your email address visible to anyone on the Internet.
Your reply message has not been sent.
Your post was successful
 
From:
To:
Cc:
Followup To:
Add Cc | Add Followup-to | Edit Subject
Subject:
Validation:
For verification purposes please type the characters you see in the picture below or the numbers you hear by clicking the accessibility icon. Listen and type the numbers you hear
 
Alan J. Flavell  
View profile  
 More options Sep 6 2000, 6:42 am
Newsgroups: comp.lang.perl.misc
From: "Alan J. Flavell" <flav...@mail.cern.ch>
Date: Wed, 6 Sep 2000 12:25:43 +0200
Local: Wed, Sep 6 2000 6:25 am
Subject: Re: CGI.pm: controlling Back & Reload

On Wed, 6 Sep 2000, David Efflandt wrote:
> The first time the script is accessed with no parameters (to generate the
> first form), test the referer() and set it to a default (like your home
> page) if referer() does not have a value.  Then pass this as a hidden
> variable through your forms and use that for your own back link on the
> last form (assuming CGI.pm function mode).

You give an ominous impression of having failed to read Abigail's
classic web page on the topic.  What you're creating is a forward link
(all links are forward links in that sense), that might or might not
take the hon. usenaut forward to the place they came from, leaving
them even more confused than they were before.

And your procedures will have no effect on "the Back button", which
was what the OP was asking about.

And, I'd surmise, still not solving the real problem that the OP is
really concerned about.

I'd recommend the OP to take on board the fact that on the WWW,
browser Back and Reload buttons do what they are designed to do, and
users expect them to do that.  Any attempt to change that is both
misguided and ultimately doomed.  Work _with_ it, instead of trying to
fight it.  The server/script is capable of being under your control:
the user and their browser is not - they will do what they do, so
devise a solution that copes with it.  (The details of that aren't a
Perl language question, but the general issue of how to approach a
programming task seems, if I may say so, still to be on-topic for the
group).

This looks to me to be another case of "premature closure": the
questioner wanted to solve some not very clearly stated X, they
concluded that Y and Z were components of a solution, and now they're
asking how to implement Y and Z.  Take a step back, look at the bigger
picture, free yourself of this inappropriate partial solution.


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.