This content has been marked as final. Show 7 replies
> https://<url address>/2serverAuth.asp:444
That URL is malformed, isn't it? Should it not be:
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.
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.
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.
<cfhttp URL="https://<url address>:444/2serverAuth.asp"
method="POST" charset="UTF-8" throwonerror="yes"
<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)">
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.