winterheat — 2008-09-20T10:31:37-04:00 — #1
In some situation where we does an <iframe src="..."> </iframe>, the URL can be longer than 2083 bytes long and it seems it will choke IE 6 and 7. Even though Apache 2.x supports URL up to 8k long, IE will not work when the URL is longer than 2083 bytes.
All the params should be short, except one that is like "user_review", which can be any length, depending on how long the user wrote.
Also a catch might be that, if we also specify a src=" ... " for the iframe initially, then the iframe might start loading first, and then all of a sudden, the form will auto submit to this iframe, and then it will cause net traffic twice? (the first one being canceled but still induce some system and net overhead). Thanks.
world_wide_weird — 2008-09-20T14:22:15-04:00 — #2
Use POST instead of GET for the form method. PHP's default maximum POST data length is 8MB.
Don't put a query string in the form's action URI. Put the query string parameters in hidden form fields instead.
winterheat — 2008-09-20T14:36:50-04:00 — #3
yes, i forgot to mention it is POST. and it is added to the original post.
actually... using those params in the URL will work too... the target can use $GET or $POST to get them... it probably is best to make them all hidden input, but as params on the URL they work on all current browsers I tried. Thank you though.
felgall — 2008-09-20T17:06:38-04:00 — #4
If you use POST then the limit on how much data you can pass is so high that it would take someone several days of typing in the form to overflow it.
If you use POST then the form fields do not end up in the URL so if it is in the URL then you are using GET rather than POST.
winterheat — 2008-09-21T01:18:33-04:00 — #5
the fact is you can post to a target with params on the URL and both POST and GET params will be passed to the php file.