If you can check the CXF source code (I don't have it with me immediately, but search the source code for the error message you're getting to determine the class) -- you can place debugging statements on what CXF thinks the hostname URL and the CN is to determine why it is failing on you. Perhaps I made a mistake in my logic someplace--but as no one else has complained about this yet, I would suspect, for some reason, your CN actually isn't matching the hostname URL.
Glen wonderingWV wrote: > > I understand why it was done, but the problem is I cannot get ssl with cxf > to work unless the flag is set to true, which I do not want to do in a > production environment. > > > Glen Mazza wrote: >> >> I'm unsure what the problem is. I had done that last March[1] after >> agreement with the team. >> >> Glen >> >> [1] http://www.jroller.com/gmazza/date/20080329 >> >> >> wonderingWV wrote: >>> >>> The common name on the cert and the hostName of the url match up so I >>> not sure why I continue to receive this error. Any advise would be >>> greatly appreciated. >>> >> >> > > -- View this message in context: http://www.nabble.com/Http-conduit-disableCNCheck-tp20444655p20445064.html Sent from the cxf-user mailing list archive at Nabble.com.
