[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Bug-wget] wget post needs better docs

From: Fernando Cassia
Subject: Re: [Bug-wget] wget post needs better docs
Date: Wed, 18 Feb 2009 18:17:57 -0200

On Wed, Feb 18, 2009 at 5:51 PM, Daniel Stenberg <address@hidden> wrote:
> On Wed, 18 Feb 2009, Micah Cowan wrote:
>>> Well this is no big deal, I mean, I could probably stick the username and
>>> password at the beginning of the file. The crux of the matter here is if it
>>> would accept a file full of CR/LF chars.... or does it also expect the file
>>> to have the whole string on a single line??
>> I believe all CR/LF have to be percent-encoded, everything on one line. It
>> probably depends somewhat on the server.
> Just note that very very few "file uploads" over HTTP are done that way. The
> typical way is to do multipart formposts (RFC1867), and they don't use
> percent-encoding at all...

For the 99st time.... I don't want to upload a file!! :-)

I have a web form at http://server.blah/sendmessage.php

As part of the form are vars "Login" "password" and "message".
Message on the form is one big (80 chars wide by several columns deep)
text entry field where you're supposed to type a long message and
click SEND.

Now I want to automate that process by first getting some data from
another server, which IS ALREADY in text (ascii - NOT even HTML so I
save the conversion step) format with Wget, save it to a file
message.txt, and then invoke wget to http-post that retrieved data
(along with username and password) to the

Hope I've made my point clearer now.

There is no file to "upload" just some data in a web form that needs
to be filled with text (including CR/LF) taken from a file.

I don't know if that makes any difference. But it certainly seems
different from doing a binary file upload over http...


reply via email to

[Prev in Thread] Current Thread [Next in Thread]