As suggested, I left only

curl -d "LoginID=xxxxxx&Pwd=yyyyy"

and substituted all four special characters with their hex ascii codes.
The response didn't change. I've got back the same original page as
before. I'm dealing with an asp page in this case. Does this make any
difference for curl?

-Mark

> -----Original Message-----
> From: curl-users-bounces_at_cool.haxx.se
> [mailto:curl-users-bounces_at_cool.haxx.se]On Behalf Of Daniel Stenberg
> Sent: Friday, February 11, 2005 6:16 PM
> To: curl tool talk
> Subject: Re: Authenticating via https form
>
>
> On Fri, 11 Feb 2005, Mark Eyman wrote:
>
> > curl 7.11.1 (i686-pc-cygwin) libcurl/7.11.1 OpenSSL/0.9.7e
> zlib/1.2.2
>
> I realize this is the version you get pre-packaged with
> cygwin, just be aware
> that this is getting rather old.
>
> > <form action="uldconfirm.asp" method="post" name = "loginform">
> > <input type="text" name="LoginID" size="20">
> > <input type="password" name="Pwd" size="20">
> > <INPUT TYPE="submit" VALUE="Submit">
> > </form>
> >
> > curl -d "LoginID=xxxxxx&Pwd=yyyyy&=Submit"
> > https://www.theurl.com/condev/uld.asp
>
> The submit won't be sent like that, as it has no name. It
> will only be:
>
> "LoginID=xxxxxx&Pwd=yyyyy"
>
> but...
>
> > 1. My password contains some special characters: (%!). The "!" in
> > particular, made bash to return an error: "bash: !: event
> not found". I put
> > a single quote " ' " in front of the "!".
>
> You must make sure the data you send is url-encoded. Special
> characters must
> be converted to their %HH versions.
>
> --
> Daniel Stenberg -- http://curl.haxx.se -- http://daniel.haxx.se
> Dedicated custom curl help for hire: http://haxx.se/curl.html
>
>
Received on 2005-02-14