[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: HTTP/1.1 412 Precondition Failed
Hi,
Sorry for my confusion, I was looking at the wrong dump again.
We had two links (a "main" URL and a 2nd URL in case the first fails) my program was trying both, and the second was giving me a different message & overlaying the dump. Obviously the backup link isn't set up correctly. I've sent that issue off to my Operations manager. For now I'm only hitting the main URL so that the dump doesn't get overlaid.
I now found the correct dump, the one where the Precondition failed. It gave me the information I needed.
Apparently there's Security information I'm missing.
I'm going to work with Chase Paymentech to resolve it.
Thanks, and again, sorry for my confusion..
Charlie
-----Original Message-----
From: ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx [mailto:ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx] On Behalf Of Scott Klement
Sent: Thursday, February 25, 2010 7:41 PM
To: HTTPAPI and FTPAPI Projects
Subject: Re: HTTP/1.1 412 Precondition Failed
Hi Charles,
"route to remote host not available" means "you cannot here there from
here." In other words, your network does not provide a way to connect
from the computer where HTTPAPI is running to the server it's trying to
connect to.
This is a TCP/IP configuration problem, and really has nothing to do
with HTTPAPI (it applies to any/all TCP/IP software connecting to that
same host.)
HOWEVER... you weren't getting this error yesterday. you were getting
a '412 Precondition Failed' which is really interesting to me because it
means you connected successfully. And you can't connect successfully if
your TCP/IP routing is configured wrong.
Think of it like a telephone call. HTTPAPI is "calling" another program
(an HTTP server) on another computer. Once the call has been answered,
it will "talk" to that computer, this is how HTTP sends/receives data.
The "route" error means that it can't complete the phone call. Consider
if your company's internal telephone system was disconnected from the
telephone company. you'd still be able to call other extensions within
the organization, but you wouldn't be able to call outside of the
organization. That's basically what a "no route to host" message means.
The "412" error means that you successfully made the call. You are
talking to someone on the other end, and that person said "Sorry
Charlie... I can't help you because <insert reason here>".
Those are two very different things. If the person you're talking to
says "Sorry Charlie" you don't think something is wrong with your
telephone and start investigating whether the cables are plugged in
correctly! Indeed, the fact that you spoke to someone would be proof
that your phone system *is* working.
The same is true here. That 412 error "proved" to me that you had
TCP/IP configured properly, and that you were providing some bad option
in your code. But now we've backslided, and your system isn't even
routed properly anymore...
And it's clearly not Paymenttech. (That would be trying to order a
pizza on the phone, and getting a message saying "our PBX isn't
connected to the telephone company", then blaming the pizza delivery
service.)
On 2/25/2010 12:38 PM, Versfelt, Charles wrote:
> I probably should have provided the whole thing...
>
> 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.
> ************End of Data********************
>
>
>
> -----Original Message-----
> From: Versfelt, Charles
> Sent: Thursday, February 25, 2010 9:17 AM
> To: 'ftpapi@xxxxxxxxxxxxxxxxxxxxxx'
> Subject: RE: HTTP/1.1 412 Precondition Failed
>
>
> Hi,
>
> 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.
>
> Charlie
> -----------------------------------------------------------------------
> 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
-----------------------------------------------------------------------