The difference this time is the '*.domain.net', previously it was for a determined sub domain so an aaddition to the host file resolved it.
I've trid a number of things with the host file but as it's a wildcard I don't see what I would add to the hosts as any number of subdomains on domain.net could resovle to a number of IP's.
Fig Leaf Software is a Service-Disabled Veteran-Owned Small Business
(SDVOSB) on GSA Schedule, and provides the highest caliber vendor-
authorized instruction at our training centers, online, or onsite.
You do not have permission to delete messages in this group
Copy link
Report message
Show original message
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
to ColdFusion Technical Talk
I've tried it that way but no dice, let show you what I have tried:
1) Exported the cert and imported into the Truststore (this should not have
been needed as it is a Thawte issued certificate which is already in the
trsutstore and lack of record in the truststore causes a different IO
error). This caused no change.
2) The live API is api.domain2.com initially this gave the error:
(note: real domain names replaced with "domain1" and "domain2")
restarted CF and called prelease-api.domain1.net in my CFHTTP request and I
get a 404 error, so I no longer get the IO error but I'm not hitting the
correct server/application
You do not have permission to delete messages in this group
Copy link
Report message
Show original message
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
to ColdFusion Technical Talk
> 3) The dev API is (real domain names replaced with "domain1" and domain2)
> prerelease-api.domain2.com initially this gave the error:
>
> I/O Exception: Name in certificate `*.domain1.net' does not match host name
> `prelease-api.domain2.com'
>
> I tried adding to the hosts:
>
> xx.xxx.xxx.xxx prelease-api.domain1.net >
> where xx.xxx.xxx.xxx is the resolving IP address of prelease-api.domain2.com >
> restarted CF and called prelease-api.domain1.net in my CFHTTP request and I
> get a 404 error, so I no longer get the IO error but I'm not hitting the
> correct server/application
It's possible they're looking for host headers to figure out how to
resolve requests. You might be able to specify the host header
separately within your CFHTTP request, but I've never tried it to be
honest.
Fig Leaf Software is a Service-Disabled Veteran-Owned Small Business
(SDVOSB) on GSA Schedule, and provides the highest caliber vendor-
authorized instruction at our training centers, online, or onsite.
You do not have permission to delete messages in this group
Copy link
Report message
Show original message
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
to ColdFusion Technical Talk
Ok we've worked out the issue to this. It is caused by SNI certificates
which the current JVM does not support. Even latest default install of Railo
on Tomcat does not support this.
It seems we need to be running a JVM 1.7 or higher to support SNI which
MX7.1 will never support.
Anybody using an IIS7 + Tomcat + Railo stack running 1.7 or above?
Any advice on that setup and nay issues would be appreciated.
-----Original Message-----
From: Dave Watts [mailto:dwa...@figleaf.com]
Sent: 08 April 2015 22:47
To: cf-talk