By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
455,228 Members | 1,375 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 455,228 IT Pros & Developers. It's quick & easy.

Wierd Problems with textareas.

P: n/a
Hello everyone!

I'm having strange problems with textareas...
This is my situation:

I have a document, which opens in a pop-up, with a form (let's call it
form1).
This form contains 3 hidden fields, 3 textareas and 1 combo.
This form is intended to generate a text and send it via e-mail (I'm
using PHP for this, and the script is working fine, i guess).
Then, I have another document, which opens in a normal window, with
another form (aka Form2).
This new form have 4 hidden fields, 3 texts and one textarea. Also on
this form, I have set the enctype to multpart-formdata, and there is
the hidden of max-upload-size (which is not on the other form)
I use this form to input data into my database (also using PHP).

Now this is the problem:
I take a reasonable big text (about 4.000 chars) and enter it into one
of the textareas of form1, I may leave everithing else blank. When I
hit the submit button, nothing happens! I mean anything at all. Seems
that IE can't build the data to send.
Now whats even stranger... If I take the same text, from the same
source, and paste it on the textarea on form2 and fill all the other
fields, IT WORKS!!!!
The data is sent and everything goes well...

Does anyone have a idea of what's happening???
I don't know if I could express myself clear, so I will answer any
questions...

Thanks!
TFValdo
Jul 20 '05 #1
Share this Question
Share on Google+
7 Replies


P: n/a
Change your form method to post. If method="get", there's a 255 character
limit to form input.

Regards,
Peter Foti
Jul 20 '05 #2

P: n/a
"Peter Foti" <pe***@Idontwantnostinkingemailfromyou.com> wrote in message news:<10************@corp.supernews.com>...
Change your form method to post. If method="get", there's a 255 character
limit to form input.


Thanks!!!
and I was almost killing myself for this to work...
Jul 20 '05 #3

P: n/a
On Thu, 15 Jan 2004, Peter Foti wrote:
If method="get", there's a 255 character limit to form input.


Where do you get *that* from?

There's certainly _some_ implementation limit to the amount of data
that can be submitted with GET, but it's been many years since the
practical limit was less than about 1K. Last time I looked, most
implementations seemed happy with 32K, or more.

There are basic fundamental reasons for choosing GET versus POST,
depending on what the script is meant to do (prime keyword:
idempotence). Sometimes there can be supervening practical reasons for
using POST when GET would otherwise have been apt (for example if the
amount of data is potentially unlimited, or there can be other
practical reasons, one of which we are seeing here).

The _real_ reason, it seems to me, that the hon Usenaut is screwing up
is that we are told that the form submission content-type is set to
multipart/formdata, which is unavailable for GET. So the solution is
either to change back to the default form submission content-type,
which is application/x-www-form-urlencoded , or to change from GET to
POST.

Which option to prefer depends on other details, which don't seem to
be evident here. But if the script is making a permanent change, or
more accurately "if the script mustn't be repeated arbitrarily"
(non-idempotent), then POST is the mandatory choice.

So it seems to me that you gave what could very well be the right
solution, but for the wrong reason.

all the best
Jul 20 '05 #4

P: n/a
"Alan J. Flavell" <fl*****@ph.gla.ac.uk> wrote in message
news:Pi*******************************@ppepc56.ph. gla.ac.uk...
On Thu, 15 Jan 2004, Peter Foti wrote:
If method="get", there's a 255 character limit to form input.
Where do you get *that* from?

<snip> So it seems to me that you gave what could very well be the right
solution, but for the wrong reason.


Alan, it looks as though you are correct, and I gave the wrong reason. I
thought I had read something a long time ago about a 255 limit when using
GET, but the closest thing I can find now is a remark in the HTTP 1.1 spec
that says:

Note: Servers ought to be cautious about depending on URI lengths
above 255 bytes, because some older client or proxy
implementations might not properly support these lengths.

But that's more of a suggestion than a limitation.

My bad.
Regards,
Peter Foti
Jul 20 '05 #5

P: n/a
On Mon, 19 Jan 2004, Peter Foti wrote:
"Alan J. Flavell" <fl*****@ph.gla.ac.uk> wrote in message
Where do you get *that* from?

[RFC2616] Note: Servers ought to be cautious about depending on URI lengths
above 255 bytes, because some older client or proxy
implementations might not properly support these lengths.
OK, fair comment...
But that's more of a suggestion than a limitation.


My apologies for bawling you out on this - I had honestly forgotten
that RFC2616 had this value, if only as a recommendation. Of course,
that RFC is dated 1999... and even then it only referred to it as a
limitation of "older" clients and proxies.

I'm confident that by now it's being over-conservative.

all the best
Jul 20 '05 #6

P: n/a
"Alan J. Flavell" <fl*****@ph.gla.ac.uk> wrote:
There's certainly _some_ implementation limit to the amount of data
that can be submitted with GET, but it's been many years since the
practical limit was less than about 1K. Last time I looked, most
implementations seemed happy with 32K, or more.


I haven't carried out any tests, but the Microsoft page
http://support.microsoft.com/default...;EN-US;q208427
says:
"Internet Explorer has a maximum uniform resource locator (URL) length
of 2,083 characters, with a maximum path length of 2,048 characters."
(originally published in 2000, but carrying the text "Last Reviewed:
5/12/2003 (2.0)" and listing IE 5.5 - though not 6.0 - as a version
to which it applies).

--
Yucca, http://www.cs.tut.fi/~jkorpela/
Pages about Web authoring: http://www.cs.tut.fi/~jkorpela/www.html

Jul 20 '05 #7

P: n/a
On Wed, 21 Jan 2004, Jukka K. Korpela wrote:
"Alan J. Flavell" <fl*****@ph.gla.ac.uk> wrote:
There's certainly _some_ implementation limit to the amount of data
that can be submitted with GET, but it's been many years since the
practical limit was less than about 1K. Last time I looked, most
implementations seemed happy with 32K, or more.


I haven't carried out any tests, but the Microsoft page
http://support.microsoft.com/default...;EN-US;q208427
says:
"Internet Explorer has a maximum uniform resource locator (URL) length
of 2,083 characters, with a maximum path length of 2,048 characters."
(originally published in 2000, but carrying the text "Last Reviewed:
5/12/2003 (2.0)" and listing IE 5.5 - though not 6.0 - as a version
to which it applies).


Oh dear. Thanks for posting the correction! I don't recall where I
put my tests, or how long ago it was, sorry; so I don't think I'm
likely to be posting any fresh test results. Which means I'd better
withdraw my previous assertion, and apologise for any confusion
caused.

I guess it's still fair to say that 255 is overly conservative for
present circumstances, though?

all the best
Jul 20 '05 #8

This discussion thread is closed

Replies have been disabled for this discussion.