Re: HTTP/1.1 412 Precondition Failed

["Loek Maartens" <l.maartens@xxxxxxxxx>]

Charles,

Where in the log is there any mention of the HTTP/1.1 412 Precondition 
failed?

Loek.

----- Original Message ----- 
From: "Versfelt, Charles" <CVERSFELT@xxxxxxxxx>
To: "'HTTPAPI and FTPAPI Projects'" <ftpapi@xxxxxxxxxxxxxxxxxxxxxx>
Sent: Thursday, February 25, 2010 9:12 PM
Subject: RE: HTTP/1.1 412 Precondition Failed


> Oops... okay, I figured out why I had the wrong dump.
> One of those Homer Simpson "D'oh!" moments...
>
> Now, let me try again...
>
> Here's the dump...
> Looks like a problem on Paymentech's end?
>
> HTTPAPI Ver 1.23 released 2008-04-24
> OS/400 Ver V5R4M0
>
> http_url_post_stmf(): entered
> getting post file size...
> opening file to be sent...
> opening file to be received
> http_persist_open(): entered
> http_long_ParseURL(): entered
> DNS resolver retrans: 2
> DNS resolver retry  : 2
> DNS resolver options: x'00000136'
> DNS default domain: xx.xxxx.xxxx
> DNS server found: xx.x.x.xxx
> DNS server found: xx.x.x.xxx
> DNS server found: xx.x.x.xxx
> SetError() #6: connect(): A route to the remote host is not available.
> http_url_post_stmf(): entered
> getting post file size...
> opening file to be sent...
> opening file to be received
> http_persist_open(): entered
> http_long_ParseURL(): entered
> DNS resolver retrans: 2
> DNS resolver retry  : 2
> DNS resolver options: x'00000136'
> DNS default domain: xx.xxxxx.xxxxx
> DNS server found: xx.x.x.xxx
> DNS server found: xx.x.x.xxx
> DNS server found: xx.x.x.xxx
> ----------------------------------------------------------------
> Dump of server-side certificate information:
> ----------------------------------------------------------------
> Cert Validation Code = 0
> -----BEGIN CERTIFICATE-----
> MIIEYTCCA8qgAwIBAgIQEtR5Os93IbLsxfawXhPCYjANBgkqhkiG9w0BAQUFADCB
> ujEfMB0GA1UEChMWVmVyaVNpZ24gVHJ1c3QgTmV0d29yazEXMBUGA1UECxMOVmVy
> aVNpZ24sIEluYy4xMzAxBgNVBAsTKlZlcmlTaWduIEludGVybmF0aW9uYWwgU2Vy
> dmVyIENBIC0gQ2xhc3MgMzFJMEcGA1UECxNAd3d3LnZlcmlzaWduLmNvbS9DUFMg
> SW5jb3JwLmJ5IFJlZi4gTElBQklMSVRZIExURC4oYyk5NyBWZXJpU2lnbjAeFw0w
> ODA4MDgwMDAwMDBaFw0xMDA4MDgyMzU5NTlaMIGkMQswCQYDVQQGEwJVUzEQMA4G
> A1UECBMHRmxvcmlkYTEOMAwGA1UEBxQFVGFtcGExKDAmBgNVBAoUH0NoYXNlIFBh
> eW1lbnRlY2ggU29sdXRpb25zLCBMTEMxJDAiBgNVBAsUG0VudGVycHJpc2UgV2Vi
> IEFyY2hpdGVjdHVyZTEjMCEGA1UEAxQab3JiaXRhbHZhcjEucGF5bWVudGVjaC5u
> IEFyY2hpdGVjdHVyZTEjMCEGA1UEAxQab3JiaXRhbHZhcjEucGF5bWVudGVjaC5u
> ZXQwgZ8wDQYJKoZIhvcNAQEBBQADgY0AMIGJAoGBALQ7JPwROTHews/OhMpCmipT
> 6T/tvOTYp7KbogWBXpKpcTBxOe4iB9y1rN+Vig5MaU1CFcKtU4ApGhymLzvcuj1/
> M+6MjI6P5CDyYf0m05mmJ+MJ7YuOaVaLdJ8QB1/13L6gqIIbed/40Q27Sfk78/hj
> DN8PiINIKJvg0N4iEMtZAgMBAAGjggF6MIIBdjAJBgNVHRMEAjAAMAsGA1UdDwQE
> AwIFoDBGBgNVHR8EPzA9MDugOaA3hjVodHRwOi8vY3JsLnZlcmlzaWduLmNvbS9D
> bGFzczNJbnRlcm5hdGlvbmFsU2VydmVyLmNybDBEBgNVHSAEPTA7MDkGC2CGSAGG
> +EUBBxcDMCowKAYIKwYBBQUHAgEWHGh0dHBzOi8vd3d3LnZlcmlzaWduLmNvbS9y
> cGEwKAYDVR0lBCEwHwYJYIZIAYb4QgQBBggrBgEFBQcDAQYIKwYBBQUHAwIwNAYI
> KwYBBQUHAQEEKDAmMCQGCCsGAQUFBzABhhhodHRwOi8vb2NzcC52ZXJpc2lnbi5j
> b20wbgYIKwYBBQUHAQwEYjBgoV6gXDBaMFgwVhYJaW1hZ2UvZ2lmMCEwHzAHBgUr
> DgMCGgQUS2u5KJYGDLvQUjibKaxLB4shBRgwJhYkaHR0cDovL2xvZ28udmVyaXNp
> Z24uY29tL3ZzbG9nbzEuZ2lmMA0GCSqGSIb3DQEBBQUAA4GBAGu1cyX5HoCoUKIX
> 0qF/l/8wNKWUvw8eyy6o8x0+v/gK0eQADDRo/pqTRfZGjrEtYXsXhmIxQsJgHTtL
> Ai2mP2U1OpPrC2rbUg0bMQotF26uWr2BMWDiMUQkoqDBiWnIegPLxj/ooFJZWTBq
> Ai2mP2U1OpPrC2rbUg0bMQotF26uWr2BMWDiMUQkoqDBiWnIegPLxj/ooFJZWTBq
> x8AY+E2FUFTvvkMKNNVqgzRDO80l
> -----END CERTIFICATE-----
> Serial Number: (serial number)
> Common Name: orbitalvar1.paymentech.net
> Country: US
> State/Province: Florida
> Locality: Tampa
> Org Unit: Chase Paymentech Solutions, LLC
> Org: Enterprise Web Architecture
> Issuer Org: VeriSign Trust Network
> Issuer Org Unit: www.verisign.com/CPS Incorp.by Ref. LIABILITY LTD.(
> Version: 03
> not before: 20080807190000
> not after: 20100808185959
> not after: 20100808185959
> pub key alg: x.x.xxx.xxxxxx.x.x.x
>
> Protocol Used: TLS Version 1
> http_persist_post(): entered
> http_long_ParseURL(): entered
> do_post(): entered
> POST /authorize/ HTTP/1.1
> Host: orbitalvar1.paymentech.net
> User-Agent: http-api/1.23
> Content-Type: text/xml
> Expect: 100-continue
> Content-Length: 692
>
>
> -----Original Message-----
> From: ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx 
> [mailto:ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx] On Behalf Of Scott Klement
> Sent: Thursday, February 25, 2010 12:10 PM
> To: HTTPAPI and FTPAPI Projects
> Subject: Re: HTTP/1.1 412 Precondition Failed
>
> I thought you were getting a "Precondition Failed"??  Now I'm really
> confused.
>
> On 2/25/2010 8:17 AM, Versfelt, Charles wrote:
>>
>> I coded for and found the debug log.
>> The problem seems to be:
>>
>> SetError() #6: connect(): A route to the remote host is not available.
> -----------------------------------------------------------------------
> This is the FTPAPI mailing list.  To unsubscribe, please go to:
> http://www.scottklement.com/mailman/listinfo/ftpapi
> -----------------------------------------------------------------------
> -----------------------------------------------------------------------
> This is the FTPAPI mailing list.  To unsubscribe, please go to:
> http://www.scottklement.com/mailman/listinfo/ftpapi
> ----------------------------------------------------------------------- 

-----------------------------------------------------------------------
This is the FTPAPI mailing list.  To unsubscribe, please go to:
http://www.scottklement.com/mailman/listinfo/ftpapi
-----------------------------------------------------------------------