ISA Server changes HTTPS requests to HTTP:// requests when SSL bridging. Urgent help needed to stop this.

I have had an existing SSL bridge working. I have just changed the certificate and the rule has stopped functioning.
I believe the cause to be that the url is being translated to a HTTP:// format from a standard HTTPS:// type url.
I really need to make sure that ISA 2004 passes on the HTTPS in the URL. If not I get the following probs...

I get the following error in IE:
Bad Request
Your browser sent a request that this server could not understand.
Request header field is missing colon separator.

iewslive/ HTTP/1.1
Oracle HTTP Server Powered by Apache/1.3.19 Server at Port 443

and the following error on my SSL Apache server.
[20/Nov/2006 10:43:00 02040] [error] SSL handshake failed: HTTP spoken on HTTPS port; trying to send HTML error page (OpenSSL library error follows)
[20/Nov/2006 10:43:00 02040] [error] OpenSSL: error:1407609C:SSL routines:SSL23_GET_CLIENT_HELLO:http request [Hint: speaking HTTP to HTTPS port!?]
Who is Participating?
DarthModConnect With a Mentor Commented:
Closed, 500 points refunded.
Community Support Moderator
Keith AlabasterEnterprise ArchitectCommented:
have you got all of the isa2004 service packs and rollup patches installed? There were a couple of issues 'fixed' by SP2 then corrected again by the follow up patches.

How are you bridging? https - https?
Have you tried backuping up the config then deleting the publishing rule then recreating it? has anything changed in the config/status recently beside the change of certificates?

If you open the ISA gui, select monitoring - logging - click on start query, what do you see in the log? it won't be much as obviously ISA cannot determine what is in the encrypted pipes but you should see any failures or translations at the point ISA tries to create the bridged connection.

If you view the certificates themselves, any issues seen with them? ISA may revert to http if the certificate is not validated as the environment for SSL would not be met.


ner_1808Author Commented:
I can browse from the ISA server to the offending Web server using the HTTPS:// url format.
However I get as above when using the HTTP:// url format, which is what is logged in ISA as the URL when attempting an external connection.
The error returned to the browser is
Error Code:500 Internal Server Error. The target principal name is incorrect (-2146893022)

However I think this is misleading as I can use the exact url from the ISA machine itself going direct to the web server. We have partitioned the DNS internally and externally.

When I browse to the server from the ISA machine the Certificate loads up fine. It is a wildcard certificate so is used fo several other HTTPS to HTTP bridging and works fine externally.

As far as changes go, other than replacing the certificate on one of the listeners I have now attempted to create new rules using the wizard, but the result is the same.
Protect Your Employees from Wi-Fi Threats

As Wi-Fi growth and popularity continues to climb, not everyone understands the risks that come with connecting to public Wi-Fi or even offering Wi-Fi to employees, visitors and guests. Download the resource kit to make sure your safe wherever business takes you!

Keith AlabasterEnterprise ArchitectCommented:
Can you give details on the certificate that has been placed on the ISA server? Creating the connection from the ISA directly will initiate a single-hop connection and will not use the ISA's certificate as an authenticator. Also, generating the connection from the ISA server is a different scenario; the source will be the internal nic of the ISA server and therefore does not use the pass-through/bridging elements that are contained within the rule.

ner_1808Author Commented:
I have finally solved this problem. Much wasted time with erroneous error messages. It turns out that ISA Server 2004 is designed to NOT accept wildcard certificates used internally. Only external wildcard certificates allowed and internal ones must be single host named ones. It would be nice if the ISA logs indicated that this might be the issue and I could have saved about 15 hours of research and attempted fixing.

Thanks for your help anyway.
Keith AlabasterEnterprise ArchitectCommented:
Your info is correct hence the direction of my questions to you

<< Can you give details on the certificate that has been placed on the ISA server >>
<< If you view the certificates themselves, any issues seen with them? ISA may revert to http if the certificate is not validated as the environment for SSL would not be met.  >>

This position is stated on a number of Microsoft forums and is also mentioned on a number of ISA questions I have resolved in the past here on Experts-Exchange. Probably my fault, I should have asked 'what is the difference between the certificate that worked and now?'.

ner_1808Author Commented:
I should have mentioned that I was using wildcard certificates! I probably would have if any of the errors or logs had indicated that there was an issue with the cert. Live and learn!
Thanks for your help anyway. Much appreciated.
Keith AlabasterEnterprise ArchitectCommented:
Keith AlabasterEnterprise ArchitectCommented:
OK with me
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.