RE: Passing cookies during session
Date: Tue, 22 Jan 2002 17:17:07 -0500
That's an easy one - the Set-Cookie lines from verbose output end up in
your output file (e.g. file_I_want_to_download.tar.gz isn't a valid
tar.gz file now, even if the download *were* working... because it's got
the response headers in it).
Can you post the headers from the top of your output file?
I've been bitten by this one on more than one occasion. Is there any way
to make the response headers become part of the stdout (to-screen)
output instead of becoming part of the output file? I assume the ability
to have them as part of the output file should still remain (for
multi-file transfers where the user wants to see 'em in the files) but
my opinion is that the default behavior should be for -v output to go to
stdout in all cases.
From: Lara Bordick [mailto:lbordick_at_interconnect.net]
Sent: Tuesday, January 22, 2002 4:49 PM
I am attaching the standard output from running the single command:
curl -v -i -b cookies --cert my_cert.pem:password -L
I still do not see any Set-Cookie lines in this output. I am not sure
if I am doing something wrong when I execute the command.
When I run the command curl -v -i -D cookies --cert my_cert.pem:password
-L https://validationserver.somesite.com I see that the server is
definitely setting the cookies with the domain = .somesite.com.
Please let me know if you would like to see any output from further
Received on 2002-01-22