I'm sorry I'm out of my depth with this one - which isn't difficult.

WORKING VERSION FROM Windows NT4

== Info: About to connect() to www.a-company.co.uk port 443
== Info: Trying nnn.nnn.nnn.nnn... == Info: connected
== Info: Connected to www.a-company.co.uk (nnn.nnn.nnn.nnn) port 443
== Info: error setting certificate verify locations, continuing anyway:
== Info: CAfile: /usr/local/share/curl/curl-ca-bundle.crt
  CApath: none
== Info: SSLv2, Client hello (1):
<= Send SSL data, 130 bytes (0x82)
0000: ....i......9..8..5..............3..2../...........f.............
0040: .c..b..a...........@..e..d..`.....................O.17.c\.r.....
0080: ..
== Info: SSLv3, TLS handshake, Server hello (2):
<= Recv SSL data, 74 bytes (0x4a)
0000: ...F..B.....Jq.0....*....~5c}.W.hx.... a...F....\....D.>|c......
0040: .x.../....
== Info: SSLv3, TLS handshake, CERT (11):
<= Recv SSL data, 2636 bytes (0xa4c)
0000: ...H..E...0...0............./......<.6....0...*.H........0..1.0.
<snip>
09c0: ............:.$o..6l.:s9..j.i...o......).!.W.U{0..d....p<vt.*..F
0a00: g2..K....V..r...u..W.q...:.K..........E%.......2".!....4.0D...
0a40: ........(:..
== Info: SSLv3, TLS handshake, Server finished (14):
<= Recv SSL data, 4 bytes (0x4)
0000: ....
== Info: SSLv3, TLS handshake, Client key exchange (16):
<= Send SSL data, 70 bytes (0x46)
0000: ...B.@.^&L....slnF._at_jj.......L.q>.G..pou4.(..fg..+Gh..t...W.AN..
0040: .....d
== Info: SSLv3, TLS change cipher, Client hello (1):
<= Send SSL data, 1 bytes (0x1)
0000: .
== Info: SSLv3, TLS handshake, Finished (20):
<= Send SSL data, 16 bytes (0x10)
0000: ........`X.7....
== Info: SSLv3, TLS change cipher, Client hello (1):
<= Recv SSL data, 1 bytes (0x1)
0000: .
== Info: SSLv3, TLS handshake, Finished (20):
<= Recv SSL data, 16 bytes (0x10)
0000: ..../......j.X.T
== Info: SSL connection using RC4-MD5
== Info: Server certificate:
== Info: subject: /C=GB/2.5.4.17=PL6 8BX/ST=Devon/L=Plymouth/2.5.4.9=Derriford/2.5.4.9=Tamar Science Park/2.5.4.9=ITTC Building/O=eProsper Ltd/OU=InstantSSL Pro/CN=www.a-company.co.uk
== Info: start date: 2004-11-02 00:00:00 GMT
== Info: expire date: 2006-12-04 23:59:59 GMT
== Info: common name: www.a-company.co.uk (matched)
== Info: issuer: /C=GB/O=Comodo Limited/OU=Comodo Trust Network/OU=Terms and Conditions of use: http://www.comodo.net/repository/OU=(c)2002 Comodo Limited/CN=Comodo Class 3 Security Services CA
== Info: SSL certificate verify result: error number 1 (20), continuing anyway.
=> Send header, 1290 bytes (0x50a)
0000: POST /acompany2/HTTPFileReceive.asp?LoginID=username&Pass=password

-----------------------------------------------------------

NOT WORKING FROM Windows 2003
== Info: About to connect() to www.a-company.co.uk port 443
== Info: Trying nnn.nnn.nnn.nnn... == Info: connected
== Info: Connected to www.a-company.co.uk (nnn.nnn.nnn.nnn) port 443
== Info: error setting certificate verify locations, continuing anyway:
== Info: CAfile: /usr/local/share/curl/curl-ca-bundle.crt
  CApath: none
== Info: SSLv2, Client hello (1):
<= Send SSL data, 130 bytes (0x82)
0000: ....i......9..8..5..............3..2../...........f.............
<snip>
09c0: ............:.$o..6l.:s9..j.i...o......).!.W.U{0..d....p<vt.*..F
0a00: g2..K....V..r...u..W.q...:.K..........E%.......2".!....4.0D...
0a40: ........(:..
== Info: SSLv3, TLS handshake, Server finished (14):
<= Recv SSL data, 4 bytes (0x4)
0000: ....
== Info: SSLv3, TLS handshake, Client key exchange (16):
<= Send SSL data, 70 bytes (0x46)
0000: ...B.@.K."....z9.GF....v}....<.........b8,.._at_W4......X..2.:8.m.T
0040: ......
== Info: SSLv3, TLS change cipher, Client hello (1):
<= Send SSL data, 1 bytes (0x1)
0000: .
== Info: SSLv3, TLS handshake, Finished (20):
<= Send SSL data, 16 bytes (0x10)
0000: ....6.4\..}....z
== Info: SSLv3, TLS change cipher, Client hello (1):
<= Recv SSL data, 1 bytes (0x1)
0000: .
== Info: SSLv3, TLS handshake, Finished (20):
<= Recv SSL data, 16 bytes (0x10)
0000: .........OpJ....
== Info: SSL connection using RC4-MD5
== Info: Server certificate:
== Info: subject: /C=GB/2.5.4.17=PL6 8BX/ST=Devon/L=Plymouth/2.5.4.9=Derriford/2.5.4.9=Tamar Science Park/2.5.4.9=ITTC Building/O=eProsper Ltd/OU=InstantSSL Pro/CN=www.a-company.co.uk
== Info: start date: 2004-11-02 00:00:00 GMT
== Info: expire date: 2006-12-04 23:59:59 GMT
== Info: common name: www.a-company.co.uk (matched)
== Info: issuer: /C=GB/O=Comodo Limited/OU=Comodo Trust Network/OU=Terms and Conditions of use: http://www.comodo.net/repository/OU=(c)2002 Comodo Limited/CN=Comodo Class 3 Security Services CA
== Info: SSL certificate verify result: error number 1 (20), continuing anyway.
=> Send header, 250 bytes (0xfa)
0000: GET /acompany2/HTTPFileReceive.asp?LoginID=username&Pass=password

Command line
curl --data-binary "@D:\filename" --header "CONTENT-TYPE: text/xml" -k "https://www.a-companyy.co.uk/HTTPFileReceive.asp?LoginID=username&Pass=password" --trace-ascii trace.txt

Regards

Richard

> -----Original Message-----
> From: Daniel Stenberg [SMTP:daniel-curl_at_haxx.se]
> Sent: Thursday, August 11, 2005 10:26 PM
> To: curl tool talk
> Subject: Re: https post problem
>
> On Thu, 11 Aug 2005, Clayton, Richard wrote:
>
> > HTTPS Post from same Windows 2003 machine to Customer2 fails -
> > Customer2 logs show this as a GET rather than a POST
>
> Use --trace-ascii in the client side to get full trace of what curl sends.
> Then figure out why the other end thinks it gets something different, or
> possibly why it DOES get something different!
>
> > This footnote also confirms that this email message has been swept for the
> > presence of computer viruses, however we cannot guarantee that this message
> > is free from such problems.
>
> I sincerely hope that you don't have to work anywhere near the guys that
> attach nonsense blurbs like this to email messages...
>
> --
> Commercial curl and libcurl Technical Support: http://haxx.se/curl.html

**********************************************************************************
This message is sent in strict confidence for the addressee only. It may
contain legally privileged information. The contents are not to be disclosed
to anyone other than the addressee. Unauthorised recipients are requested
to preserve this confidentiality and to advise the sender immediately of any
error in transmission.
This footnote also confirms that this email message has been swept for the
presence of computer viruses, however we cannot guarantee that this message
is free from such problems.
**********************************************************************************
Received on 2005-08-12