K
Kevin Blount
I love Google groups, you can find answers to ALL your questions here..
right?
I'm building a search script in ASP (not progressed to ASP.NET just
yet) and everything works. The problem I was having though was when
users move through the different pages of a set of returned results,
and then pres the browser "Back" button, they saw the "Warning: Page
has Expired" message, and had to refresh.
I fixed this by changing my form from POST to GET and now users can go
back through their browsers history and see previous pages of results.
But, and you know what's coming, GET is fugly!! I don't want all that
garbage in my URL, spoiling a nice pretty website. So, here's the
question (though I suspect I know the answer <frown>):
Is there a way to use GET but still POST the form entries? or maybe use
POST but append 1 item to the URL?
I wondering if using a temp (i.e. without an expiry date) cookie could
contain most of the info, such as search string, scope, language, etc,
and just keeping page=X in the URL. That I could live with and stick
with GET. but if I can get rid of ALL pairs from the URL, and/or go
back to using POST without the "Warning: Page has Expired" message,
then that would be ideal!
any thoughts, hints, links, etc would be most appreciated.
Kevin
right?
I'm building a search script in ASP (not progressed to ASP.NET just
yet) and everything works. The problem I was having though was when
users move through the different pages of a set of returned results,
and then pres the browser "Back" button, they saw the "Warning: Page
has Expired" message, and had to refresh.
I fixed this by changing my form from POST to GET and now users can go
back through their browsers history and see previous pages of results.
But, and you know what's coming, GET is fugly!! I don't want all that
garbage in my URL, spoiling a nice pretty website. So, here's the
question (though I suspect I know the answer <frown>):
Is there a way to use GET but still POST the form entries? or maybe use
POST but append 1 item to the URL?
I wondering if using a temp (i.e. without an expiry date) cookie could
contain most of the info, such as search string, scope, language, etc,
and just keeping page=X in the URL. That I could live with and stick
with GET. but if I can get rid of ALL pairs from the URL, and/or go
back to using POST without the "Warning: Page has Expired" message,
then that would be ideal!
any thoughts, hints, links, etc would be most appreciated.
Kevin