Its working now, I assumed from the 404 that DNS resolution has failed, so
in the URL field I included the IP of the web server, and now it is working.
Have to go back to the CF server and see whats going on. Thanks for your
help, I hadn't thought of dumping the #cfhttp# variable.

  _____  

From: Matthew Walker [mailto:[EMAIL PROTECTED]
Sent: Monday, 20 September 2004 2:25 PM
To: CF-Talk
Subject: RE: CFHTTP error

I'm assuming you pasted your URL into those two lines, right? Can you share
the URL of your CSV?

  _____  

From: Brant Winter [mailto:[EMAIL PROTECTED]
Sent: Monday, 20 September 2004 4:30 p.m.
To: CF-Talk
Subject: RE: CFHTTP error

I don't understand this, I get a 404 in the header output on that page:

Not sure if you can see that screen shot ?

  _____  

From: Matthew Walker [mailto:[EMAIL PROTECTED]
Sent: Monday, 20 September 2004 2:01 PM
To: CF-Talk
Subject: RE: CFHTTP error

OK. Have you tried ...

<cfhttp url="" url" method="GET"></cfhttp>
<cfdump var="#cfhttp#">

Does that work?

----------------------------------------------------------------
The information transmitted is intended only for the person or entity to
which it is addressed and may contain confidential and/or privileged
material. Any review, retransmission, dissemination or other use of, or
taking of any action in reliance upon, this information by persons or
entities other than the intended recipient is prohibited. If you received
this in error, please contact the sender and delete the material from any
computer. It is the responsibility of the recipient to ensure that the
onward transmission, opening or use of this message and any attachments will
not adversely affect its systems or data. Please carry out such virus and
other checks, as you consider appropriate. To the fullest extent allowed by
law, no responsibility is accepted by Haematology & Oncology Clinics of
Australasia for any virus damage caused by this message.
  _____

  _____
[Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings] [Donations and Support]

Reply via email to