Al: Yes, I have. I've got complete control of the port on the far end, so I've tried both HTTP and HTTPS urls using both standard and non standard ports, leaving them in the URL, omitting them and letting the protocol (http/https) dictate the port as well as specifying every combination of the above w/ a port="nnnn" parameter to cfhttp to no avail. Per the docs a port in the URL overrides a port="nnnn" designation, but I'm not able to get anything but the exceptions I listed.
What's weird is that w/ tcpdump and wireshark I can see things flowing, but it's almost like it doesn't fully establish a http session or something...kinda scratching my head over it at this point. Thanks, bb On Tuesday, March 22, 2016 at 4:32:19 PM UTC-4, Al Holden wrote: > > Have you tried placing 8080 into the separate "port" attribute of the > cfhttp tag? > Al > > On 3/22/2016 1:23 PM, Bryan B wrote: > > Hello: > > We have a CFHTTP call that is failing and I cannot figure out why: > > <cftry> > <cfhttp url="http://qaapp01:8080/payment-gateway/ws/"; > <http://qaapp01:8080/payment-gateway/ws/> method="post" > throwonerror="true"> > <cfhttpparam type="header" name="content-length" value="#len(soap)#"> > <cfhttpparam type="header" name="charset" value="utf-8"> > <cfhttpparam type="XML" value="#trim(soap)#"> > </cfhttp> > > <cfdump var="#cfhttp#" /> > > <cfcatch type="Any"> > <cfset attributes.msg_error="#cfcatch.detail#-#cfcatch.message#"> > </cfcatch> > </cftry> > > It doesn't matter what I adjust as far as the URL, protocol or port, I > always seem to end up with this exception: > > throwonerror=true : General Runtime Error; Unrecognized error code: > Cannot locate: Connection Failed > throwonerror=false : Failed due to invalid Protocol: null > > It seems to bubble up into Apache's HTTPClient libs, but I've reached a > dead end trying to find out why. Looking at the conversation in wireshark, > I can seem some chatter back and forth between client and server, but a > HTTP conversation never seems to take place and I don't see anything hit > the fat end's access logs. This is NOT an HTTPS call (although capable). > I've tried using HTTPS and HTTP, on standard and non-standard ports and > nothing seems to get me past this error. > > I've also verified that connectivity is good between the two hosts---I can > get a response from the far end on the requesting host using wget/CURL. > > This is OpenBD 3.1 Ready2Run running on Linux (I've tried both Linux Mint > 17.3 and Amazon Linux 2015.09) running under Java 8 64-bit, trying to make > a SOAP post to a Jetty 9.3.2 / JDK 1.8 64-bit application server running on > Amazon Linux 2015.09 . > > If any of you have ever seen anything like this or have any ideas, input > would be appreciated! > > Thanks, > Bryan > > -- > -- > online documentation: http://openbd.org/manual/ > http://groups.google.com/group/openbd?hl=en > > --- > You received this message because you are subscribed to the Google Groups > "Open BlueDragon" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected] <javascript:>. > For more options, visit https://groups.google.com/d/optout. > > > -- -- online documentation: http://openbd.org/manual/ http://groups.google.com/group/openbd?hl=en --- You received this message because you are subscribed to the Google Groups "Open BlueDragon" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
