Re: 6.1 Patch - Form Data Back Button Issue

This WebDNA talk-list message is from

2006


It keeps the original formatting.
numero = 66907
interpreted = N
texte = On 4/20/06 4:55 PM, "Donovan Brooke" wrote: > Jason Ludwig wrote: > >> I have been searching the archives for a solution to my problem, but haven't >> found a solid solution. >> >> The problem is: >> Perform a search using POST method, >> Get results, >> Use the browser "Back Buttton" in IE. >> Get an error message that says "Warning: Page has Expired" >> >> In the archives, people are talking about a 6.1 patch that fixes this >> problem, but not available in the downloads area of the SMSI website. >> Is there a 6.1 Patch? If so, how do I get it? >> >> I believe using the GET method would probably solve this problem, but I >> don't want all of my form data being posted in the url. >> >> Any Thoughts. >> Thanks > > > This is part of the html standard and is working as it should me thinks. > As I interpreted it, the post method > was originally designed to send sensitive data only once.. and to > not be able to retrieve the data once sent, if so desired. However, browsers > have, > in large part, never seem to have taken the standard in respect > to post method as literally as it sounds at w3c (to me). > Only some browsers adhere literally.. and it seems more lately > are implimenting it more literally (along with P3P and other security > methods). > When I researched this a couple years ago, I gained a good > grasp on what exactly was at play.. but its become sort of hazy at this point. > :-) > > Go to: > http://www.w3.org/ > > and you should be able to find out the correct mimeHeader combination > to get the results that you want. For a quick fix.. setting the the > pages to be cacheable and setting your expires in the future should > get rid of that message. > > Donovan > > > > Well, I decided to use the GET method to get around my problem. I used this as a fix because none of the form data is sensitive information. Now it works great, as long as I can get over the long URL. Thanks to all that posted. Jason ------------------------------------------------------------- This message is sent to you because you are subscribed to the mailing list . To unsubscribe, E-mail to: To switch to the DIGEST mode, E-mail to Web Archive of this list is at: http://webdna.smithmicro.com/ Associated Messages, from the most recent to the oldest:

    
  1. Re: 6.1 Patch - Form Data Back Button Issue ( Jason Ludwig 2006)
  2. Re: 6.1 Patch - Form Data Back Button Issue ( Donovan Brooke 2006)
  3. Re: 6.1 Patch - Form Data Back Button Issue ( devaulw@onebox.com 2006)
  4. 6.1 Patch - Form Data Back Button Issue ( Jason Ludwig 2006)
On 4/20/06 4:55 PM, "Donovan Brooke" wrote: > Jason Ludwig wrote: > >> I have been searching the archives for a solution to my problem, but haven't >> found a solid solution. >> >> The problem is: >> Perform a search using POST method, >> Get results, >> Use the browser "Back Buttton" in IE. >> Get an error message that says "Warning: Page has Expired" >> >> In the archives, people are talking about a 6.1 patch that fixes this >> problem, but not available in the downloads area of the SMSI website. >> Is there a 6.1 Patch? If so, how do I get it? >> >> I believe using the GET method would probably solve this problem, but I >> don't want all of my form data being posted in the url. >> >> Any Thoughts. >> Thanks > > > This is part of the html standard and is working as it should me thinks. > As I interpreted it, the post method > was originally designed to send sensitive data only once.. and to > not be able to retrieve the data once sent, if so desired. However, browsers > have, > in large part, never seem to have taken the standard in respect > to post method as literally as it sounds at w3c (to me). > Only some browsers adhere literally.. and it seems more lately > are implimenting it more literally (along with P3P and other security > methods). > When I researched this a couple years ago, I gained a good > grasp on what exactly was at play.. but its become sort of hazy at this point. > :-) > > Go to: > http://www.w3.org/ > > and you should be able to find out the correct mimeHeader combination > to get the results that you want. For a quick fix.. setting the the > pages to be cacheable and setting your expires in the future should > get rid of that message. > > Donovan > > > > Well, I decided to use the GET method to get around my problem. I used this as a fix because none of the form data is sensitive information. Now it works great, as long as I can get over the long URL. Thanks to all that posted. Jason ------------------------------------------------------------- This message is sent to you because you are subscribed to the mailing list . To unsubscribe, E-mail to: To switch to the DIGEST mode, E-mail to Web Archive of this list is at: http://webdna.smithmicro.com/ Jason Ludwig

DOWNLOAD WEBDNA NOW!

Top Articles:

Talk List

The WebDNA community talk-list is the best place to get some help: several hundred extremely proficient programmers with an excellent knowledge of WebDNA and an excellent spirit will deliver all the tips and tricks you can imagine...

Related Readings:

Bill To - Ship To Information display (1997) Firesite cache vs webcat cache (1997) WebCat2b13MacPlugIn - [include] doesn't allow creator (1997) Emailer (1998) Setting up shop (1997) Apple event reply error (-1) (1997) Re[2]: New syntax feedback for 4.0 (2000) Mac GUI editors (1997) 404 error page issue (2006) UPDATE PROBLEM (1997) Associative lookup style? + bit more (1997) Cookie ... Less Navigation (2001) Add a field to the error log? (1997) WebCatalog2 Feature Feedback (1996) Payment calculator ?? (2000) [WebDNA] listvariables (2014) WebCat2 - [format thousands] (1997) Using "/" for path to virtual host root ? (2003) WebCat2b13MacPlugIn - [include] (1997) WC2b15 - [HTMLx]...[/HTMLx] problems (1997)