I'm trying to figure out how to do a POST followed by a GET.
If I do something like:
wget http://www.somesite.com/post.cgi --post-data 'a=1b=2'
http://www.somesite.com/getme.html -d
I get the following behavior:
POST /post.cgi HTTP/1.0
snip
[POST data: a=1b=2]
snip
POST /getme.html HTTP/1.0
Tony Lewis [EMAIL PROTECTED] writes:
I'm trying to figure out how to do a POST followed by a GET.
If I do something like:
wget http://www.somesite.com/post.cgi --post-data 'a=1b=2'
http://www.somesite.com/getme.html -d
Well... `--post-data' currently affects all the URLs in the Wget run
Hrvoje Niksic wrote:
Maybe the right thing would be for `--post-data' to only apply to the
URL it precedes, as in:
wget --post-data=foo URL1 --post-data=bar URL2 URL3
snip
But I'm not at all sure that it's even possible to do this and keep
using getopt!
I'll start by saying that I
On Tue, 14 Oct 2003, Tony Lewis wrote:
It would be the same logically equivalent to the following three commands:
wget --user-agent='my robot' --post-data 'data=foo' POST URL1
wget --user-agent='my robot' --post-data 'data=bar' POST URL2
wget --user-agent='my robot' --referer=URL3 GET URL4
I like these suggestions. How about the following: for 1.9, document
that `--post-data' expects one URL and that its behavior for multiple
specified URLs might change in a future version.
Then, for 1.10 we can implement one of the alternative behaviors.
Hrvoje Niksic wrote:
I like these suggestions. How about the following: for 1.9, document
that `--post-data' expects one URL and that its behavior for multiple
specified URLs might change in a future version.
Then, for 1.10 we can implement one of the alternative behaviors.
That works for
