|
|
Posted by Daz on 01/15/07 05:12
Tim Roberts wrote:
> "Daz" <cutenfuzzy@gmail.com> wrote:
> >
> >Is there any particular reason that you aren't using POST? Generally,
> >GET is for getting data, and POST is for posting. Also, I believe that
> >post encodes and escapes the data, too, so it will arrive as you'd
> >expect it to.
>
> This is not true. GET and POST requests are both encoded, although they
> use different schemes. With the exception of file uploads, there is
> nothing you can send with POST that you cannot also send with GET.
What I meant by encoded, was encrypted, I think I just chose the wrong
word. I believe that POST requests are encrypted, whereas GET requests
are simply just encoded into URL format.
> HOWEVER, just because one can, doesn't mean one should. Your basic advice
> is correct: POST should almost always be used for forms, because the URLs
> get too large.
>
> >My guess is that there is not URL code for the newline
> >chracter, as it's a control code, and not meant to be visible.
>
>
> Nope. That's not the problem. Another responder nailed it: you have to
> tell the <textarea> that you want the newlines by saying <textarea
> wrap="hard">. Otherwise, it assumes you don't want the newlines at all,
> and discards them.
Well, it was just a guess (as stated). But that is a useful piece of
information to know of, and I was totally unaware of it. I personally
feel it would have been better the other way round, wrap="hard" by
default, as I think it's unlikely that you want the data in any format
other than the format is was entered. Many, many thanks for your input.
Daz.
> --
> Tim Roberts, timr@probo.com
> Providenza & Boekelheide, Inc.
Navigation:
[Reply to this message]
|