Re: [IUG] Warning: Page has Expired - Problem

["Katrina Piechnik" <kpiechnik at jenkinslaw dot org>]

I tried using the GET method for the search forms... It didn't work...
:-(.

Katrina

-----Original Message-----
From: innopac-bounces at innopacusers dot org
[mailto:innopac-bounces at innopacusers dot org] On Behalf Of Ed Seedhouse
Sent: Thursday, August 14, 2008 2:02 PM
To: IUG INNOPAC List
Subject: Re: [IUG] Warning: Page has Expired - Problem

Bob Duncan wrote:

 > Try using GET instead of POST for the method attribute in your
 > form.  Note that if you launch searches from the system-generated
 > search forms, which use GET, you won't see the warnings.

Be aware that this will truncate any search string that exceeds 256 
characters.  Given the complexity of innovative's search strings I 
suggest this may be a risky practice and cause odd results for complex 
searches.

It also puts the search paramaters in the url string where they may be 
easily read by anyone, though I doubt that's very important.

The problem described will occur for any page that uses POST anywhere on

the web and you come across it all the time.  I suspect users will be 
used to it.  POST is the "proper" way to pass such data with the HTTP 
protocol in any event.

Ed Seedhouse
Greater Victoria Public Library


> At 11:28 AM 08/14/2008, Katrina wrote:
>> Good morning, here is my challenge for the day.
>>
>> In our catalog http://jac.jenkinslaw.org/search  (rel 2007 webPro)
>> After searching for a keyword and choosing individual title from the
>> browse display
>>
>>  if I click on IE BACK button I am getting and error message
>>
>> "Warning: Page has Expired
>> The page you requested was created using information you submitted in
a
>> form. This page is no longer available. As a security precaution,
>> Internet Explorer does not automatically resubmit your information
for
>> you.
>>
>> To resubmit your information and view this Web page, click the
Refresh
>> button. "
>>
>> Do you have any idea how to fix this problem?
> 
> 
> Try using GET instead of POST for the method attribute in your 
> form.  Note that if you launch searches from the system-generated 
> search forms, which use GET, you won't see the warnings.
> 
> Bob Duncan
> 
> 
> ~!~!~!~!~!~!~!~!~!~!~!~!~
> Robert E. Duncan
> Systems Librarian
> Editor of IT Communications
> Lafayette College
> Easton, PA  18042
> duncanr at lafayette dot edu
> http://www.library.lafayette.edu/ 
> 
> 
> --
> This message was distributed through the Innovative Users Group
INNOPAC list
> Public replies:  INNOPAC at innopacusers dot org
> Update your subscription options:
http://innopacusers.org/mailman/listinfo/innopac

--
This message was distributed through the Innovative Users Group INNOPAC
list
Public replies:  INNOPAC at innopacusers dot org
Update your subscription options:
http://innopacusers.org/mailman/listinfo/innopac