Re: [IUG] Warning: Page has Expired - Problem
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
- Date: Thu, 14 Aug 2008 15:49:51 -0400
- From: Bob Duncan <duncanr at lafayette dot edu>
- Subject: Re: [IUG] Warning: Page has Expired - Problem
At 02:02 PM 08/14/2008, Ed wrote:
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
Not on our system. I just submitted a keyword search for the bulk of
a summary note, and the 500 characters in the query were processed
just fine. That said, funkiness can result when you start going over
500; the system seems to choke on generating all the required code.
. . . POST is the "proper" way to pass such data with the HTTP
protocol in any event.
Not according to the W3C. Both methods are proper, each has its use,
and in situations where bookmarking or linking are involved and the
transaction is considered safe, GET is the preferred method.
Robert E. Duncan
Editor of IT Communications
Easton, PA 18042
duncanr at lafayette dot edu