Re: Internet Explorer 6 Form problems
This WebDNA talk-list message is from 2005
It keeps the original formatting.
numero = 62622
interpreted = N
texte = I agree with almost everything you say. Except the point about having to change the processing page to handle the form. That is one of the joys of WebCat. You do not. I have been developing for at least a few days now and I have at least a day of WebCat under my belt. :) The issue at hand is not whether or not I can process the form data once passed over to the handling page, but more the timing out (Page cannot be displayed) when using the method POST. This is starting to break on sites that have worked for years. -----Original Message----- From: WebDNA Talk [mailto:WebDNA-Talk@talk.smithmicro.com] On Behalf Of Bess Ho Sent: Monday, July 18, 2005 2:31 PM To: WebDNA Talk Subject: Re: Internet Explorer 6 Form problems Many use POST because GET is not very secure in terms of security. GET is wild open that everyone with some IT knowledge can read all the parameters and hidden fields on GET form. It showed up on the URL, showing all the name and values including the hidden fields. Therefore it is easy for release sensitive information that provider or user didn't want to reveal. GET will show those parameters on URL even on a secured SSL website. It is not as simple as changing in between GET and POST. The method to pass the form field is different. If you change the form from GET to POST, you would have to change the processing page that handle the form fields. Bess Ho Business Analyst/Webmaster Dept of Marketing US Merchant Systerms 3125 Skyway Court Fremont CA 94539 Direct 510-771-2100 Ext 119 Fax 800-329-0961 bessh@usms.com www.usms.com -----Original Message----- From: Donovan Brooke [mailto:dbrooke@euca.us] Sent: Monday, July 18, 2005 1:43 PM To: WebDNA Talk Subject: Re: Internet Explorer 6 Form problems WebDna @ Inkblot Media wrote: > Let me clarify that ... It works ALL THE TIME if I change the form method > from Post to Get. It works all the time in my IE, but never in my Wife's and > some clients'. Thats what I'm talking about... POST method was originally design to send secured info (from what I can tell). If you read about it at w3 it talks about that. Basically, one should not be able to access a page that has expired via post method... (according to *an* interpretation of the standards). Also, P3P will utilize some rules for the POST method as well. It will probably have to do with the security level settings of IE, MimeHeaders, and could have something to do with P3P... but if there are no Cookies, my guess is that this is not the issue. POST *IS* different from GET.. an easy way to verify the Mimeheaders is by an outside website with that tool.. don't have time to look for one. Donovan -- =o=o=o=o=o=o=o=o=o=o=o=o=o=o=o=o=o=o=o=o=o=o=o=o=o DONOVAN D. BROOKE Euca Design Center <-Web Development (specializing in eCommerce), -> <- Graphic Design, Custom Tags and Labels -> ADDRESS:> Donovan Brooke Euca Design Center 1871 HWY MM Fitchburg, WI 53575 PH:> 1.608.835.2476 Web:> http://www.egg.bz http://www.euca.us =o=o=o=o=o=o=o=o=o=o=o=o=o=o=o=o=o=o=o=o=o=o=o=o=o ------------------------------------------------------------- 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/ ------------------------------------------------------------- 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/ ------------------------------------------------------------- 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:
I agree with almost everything you say. Except the point about having to change the processing page to handle the form. That is one of the joys of WebCat. You do not. I have been developing for at least a few days now and I have at least a day of WebCat under my belt. :) The issue at hand is not whether or not I can process the form data once passed over to the handling page, but more the timing out (Page cannot be displayed) when using the method POST. This is starting to break on sites that have worked for years. -----Original Message----- From: WebDNA Talk [mailto:WebDNA-Talk@talk.smithmicro.com] On Behalf Of Bess Ho Sent: Monday, July 18, 2005 2:31 PM To: WebDNA Talk Subject: Re: Internet Explorer 6 Form problems Many use POST because GET is not very secure in terms of security. GET is wild open that everyone with some IT knowledge can read all the parameters and hidden fields on GET form. It showed up on the URL, showing all the name and values including the hidden fields. Therefore it is easy for release sensitive information that provider or user didn't want to reveal. GET will show those parameters on URL even on a secured SSL website. It is not as simple as changing in between GET and POST. The method to pass the form field is different. If you change the form from GET to POST, you would have to change the processing page that handle the form fields. Bess Ho Business Analyst/Webmaster Dept of Marketing US Merchant Systerms 3125 Skyway Court Fremont CA 94539 Direct 510-771-2100 Ext 119 Fax 800-329-0961 bessh@usms.com www.usms.com -----Original Message----- From: Donovan Brooke [mailto:dbrooke@euca.us] Sent: Monday, July 18, 2005 1:43 PM To: WebDNA Talk Subject: Re: Internet Explorer 6 Form problems WebDna @ Inkblot Media wrote: > Let me clarify that ... It works ALL THE TIME if I change the form method > from Post to Get. It works all the time in my IE, but never in my Wife's and > some clients'. Thats what I'm talking about... POST method was originally design to send secured info (from what I can tell). If you read about it at w3 it talks about that. Basically, one should not be able to access a page that has expired via post method... (according to *an* interpretation of the standards). Also, P3P will utilize some rules for the POST method as well. It will probably have to do with the security level settings of IE, MimeHeaders, and could have something to do with P3P... but if there are no Cookies, my guess is that this is not the issue. POST *IS* different from GET.. an easy way to verify the Mimeheaders is by an outside website with that tool.. don't have time to look for one. Donovan -- =o=o=o=o=o=o=o=o=o=o=o=o=o=o=o=o=o=o=o=o=o=o=o=o=o DONOVAN D. BROOKE Euca Design Center <-Web Development (specializing in eCommerce), -> <- Graphic Design, Custom Tags and Labels -> ADDRESS:> Donovan Brooke Euca Design Center 1871 HWY MM Fitchburg, WI 53575 PH:> 1.608.835.2476 Web:> http://www.egg.bz http://www.euca.us =o=o=o=o=o=o=o=o=o=o=o=o=o=o=o=o=o=o=o=o=o=o=o=o=o ------------------------------------------------------------- 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/ ------------------------------------------------------------- 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/ ------------------------------------------------------------- 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/
"WebDna @ Inkblot Media"
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:
Search/sort in URL Was: GuestBook example (1997)
WebDNA to Apache RewriteMap (2005)
WebCatalog 4.0.1b2 is now available (2000)
process SSI (1998)
WebCat2 Append problem (B14Macacgi) (1997)
Searching for Email Address (2004)
Multiple prices per product (2004)
[WebDNA] [sendmail] mystery (2009)
total number of matches (1999)
unsubscribe (2000)
Secure server question (1997)
WebCat2b15MacPlugIn - [authenticate] not [protect] (1997)
[WebDNA] OS and version (2019)
Browser frames and URLs in the Location field (2004)
Date problems-more (1997)
Sku numbers (1997)
Large databases in WebCat (1997)
WebCat2: Items xx to xx shown, etc. (1997)
Sample Tearoom Search Error (1997)
Webcatalog and Plesk (2003)