Re: Size Limitation through a POST via SSL?
This WebDNA talk-list message is from 2005
It keeps the original formatting.
numero = 60881
interpreted = N
texte = > Looking at the source code returned in Safari there is no HTML or body > declaration.>> The source code in IE only shows .>> Maybe if you format your HTML correctly you will alleviate the problem > :)This is just a test form - there is an actual site in place that uses the same form, which does have all the proper html, head, and body tags in place. This test form was constructed so that we could test our solutions out without involving the customer's live site, but the size of the post info is about the same. I will place the tags on the page anyhow.As for what IE shows as being returned, that is it. All the post information is lost, and as such, the formvariables context does not run. If you were to call the page directly, you would see the same thing in any browser. In fact, with IE5 Mac, if you delete everything from the tenth field on down, plus remove the last 6 characters in the ninth field (so it only says 'Compan'), the form will submit. Any character added to any other field will cause the form to fail, until another character is removed to bring the number of characters down. Bear in mind that the exact character seems to vary by one or two positions sometimes (in other words, most of the time removing the last 6 characters in the ninth field will solve the problem, but sometimes it can be the last 8 to 4 characters - I suspect that this has something to do with slight variances in the mime headers).Another note... we found that adding an extremely large form element to a page will cause any browser to break. This large form element can be a file, or just text. For example, if you go to https://secure.webbuilders.com/form3.html, you will find that no browser can submit that form. But, if you access the same form at http://secure.webbuilders.com/form3.html (without the encryption), even IE5 Mac can submit the form. Clearly, there seems to be some sort of limit to what browsers can encrypt, and IE5 Mac is the smallest of them all.Dennis-------------------------------------------------------------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:
> Looking at the source code returned in Safari there is no HTML or body > declaration.>> The source code in IE only shows .>> Maybe if you format your HTML correctly you will alleviate the problem > :)This is just a test form - there is an actual site in place that uses the same form, which does have all the proper html, head, and body tags in place. This test form was constructed so that we could test our solutions out without involving the customer's live site, but the size of the post info is about the same. I will place the tags on the page anyhow.As for what IE shows as being returned, that is it. All the post information is lost, and as such, the formvariables context does not run. If you were to call the page directly, you would see the same thing in any browser. In fact, with IE5 Mac, if you delete everything from the tenth field on down, plus remove the last 6 characters in the ninth field (so it only says 'Compan'), the form will submit. Any character added to any other field will cause the form to fail, until another character is removed to bring the number of characters down. Bear in mind that the exact character seems to vary by one or two positions sometimes (in other words, most of the time removing the last 6 characters in the ninth field will solve the problem, but sometimes it can be the last 8 to 4 characters - I suspect that this has something to do with slight variances in the mime headers).Another note... we found that adding an extremely large form element to a page will cause any browser to break. This large form element can be a file, or just text. For example, if you go to https://secure.webbuilders.com/form3.html, you will find that no browser can submit that form. But, if you access the same form at http://secure.webbuilders.com/form3.html (without the encryption), even IE5 Mac can submit the form. Clearly, there seems to be some sort of limit to what browsers can encrypt, and IE5 Mac is the smallest of them all.Dennis-------------------------------------------------------------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/
"Dennis J. Bonsall, Jr."
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:
Thanks ! (1997)
New servers and new inline cache (1997)
[TaxableTotal] - not working with AOL and IE (1997)
triggers have stopped once again (2002)
Is there an alternative to emailer? (1999)
Problem 2: Prefs file... (1997)
Mac Vs WindowsNT (1997)
SOP for WebDNA talk - MSNBot Crashing (2004)
WebCatalog can't find database (1997)
Why does this not work? (2002)
More Applescript (1997)
createfolder not behaving as expected (1999)
NT BETA BUG???? (1997)
multi-table date sort problem thingy (2002)
b12 cannot limit records returned and more. (1997)
WebCatalog usage (1997)
Can this be done? (1997)
MasterCounter - Does this work?? (1999)
Follow-Up to: Removing [showif] makes a big difference in speed (1997)
same products but different (1998)