• Global community
    • Language:
      • Deutsch
      • English
      • Español
      • Français
      • Português
  • 日本語コミュニティ
    Dedicated community for Japanese speakers
  • 한국 커뮤니티
    Dedicated community for Korean speakers
Exit
0

CFHTTP Tag error

New Here ,
Jun 26, 2007 Jun 26, 2007

Copy link to clipboard

Copied

Hi,

CFHTTP tag is giving connection failure error at the same time its XML HTTP object is working, while accessing a secured URL.

Here is the code snipet used,
<cfhttp URL="https://<url address>:444/Auth.asp"
method="POST" port="444"
resolveurl="false" timeout="60">
<cfhttpparam type="Header" name="Accept-Encoding" value="deflate;q=0">
<cfhttpparam type="Header" name="TE" value="deflate;q=0">
<CFHTTPPARAM type="HEADER" name="User-Agent" value="Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.0)">
...
....

Following code is working for XML HTTP

<cfobject action="CREATE" class="MSXML2.ServerXMLHTTP.4.0" type="COM" name="objXMLHTTP">
<cfset objXMLHTTP.open("POST", "https://<url>:444/Auth.asp", False)>
<cfset objXMLHTTP.setRequestHeader("content-type", "application/x-www-form-urlencoded")>
<cfset strMessage="command=GetParam">
<cfset objXMLHTTP.send("#strMessage#")>
<cfset strResponseText = objXMLHTTP.responseText>
......
...

Test environment and scenarios we followed.

Running the application in coldfusion MX 7.01 and 7.02 enterprise version in windows 2003.
Remote application(url we are accessing) SSL used is Versign.
Error returned is "Connection Failure: Staus code unavailable" and "I/O Exception: peer not authenticated Connection Failure".

We tried all the configuration setting described in the forums and adobe websites as well as the code change recommended., but it was not useful.

Guys, what could be the reason of the above mentioned issue?

Thanks,
Prasanth



TOPICS
Advanced techniques

Views

866

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Advisor ,
Jun 27, 2007 Jun 27, 2007

Copy link to clipboard

Copied

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Community Expert ,
Jun 29, 2007 Jun 29, 2007

Copy link to clipboard

Copied

An idea. Add attributes charset and throwOnError to the cfhttp tag. remove the port attribute. Then wrap everything around try/catch. Hopefully, that should tell us a bit more if it were to fail again.

<cftry>
<cfhttp URL="https://<url address>:444/2serverAuth.asp"
method="POST" charset="UTF-8" throwonerror="yes"
resolveurl="false" timeout="60">
<cfhttpparam type="Header" name="Accept-Encoding" value="deflate;q=0">
<cfhttpparam type="Header" name="TE" value="deflate;q=0">
<CFHTTPPARAM type="HEADER" name="User-Agent" value="Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.0)">
...
....
<cfcatch type="any">
<cfdump var="#cfcatch#">
</cfcatch>

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
New Here ,
Jul 02, 2007 Jul 02, 2007

Copy link to clipboard

Copied

few questions

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
LEGEND ,
Jun 27, 2007 Jun 27, 2007

Copy link to clipboard

Copied

> https://<url address>/2serverAuth.asp:444

That URL is malformed, isn't it? Should it not be:

https://<url address>:444/2serverAuth.asp

And are you sure it should not be 443 for HTTPS? In which case you don't
need it on the URL anyhow, as HTTP defaults to 443 for HTTPS requests.

--
Adam

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
New Here ,
Jun 28, 2007 Jun 28, 2007

Copy link to clipboard

Copied

Thanks for your update.
we used https://<url address>:444/2serverAuth.asp.

For this service there is a seperate port 444 is added.The problem is not that.

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Participant ,
Jun 29, 2007 Jun 29, 2007

Copy link to clipboard

Copied

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
New Here ,
Jul 02, 2007 Jul 02, 2007

Copy link to clipboard

Copied

LATEST
I have few doubts on applying ssl certificate on java keystore of JVM.

1.) If the same server has multiple websites running, this ssl certificate implementation will effect negatively all the web application? do we can apply it only for a single web application?.
2.) What exactly applying ssl certificate on java keystore internally relates with cfhttp?
3.)We are planned to configure the same in our production environment, do we need to take any other measure not to effect other services?

Your help will be appreciated.
Thanx,

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Resources
Documentation