I have a secure site which I want to publish in mainly HTTP and only certain pages in HTTPS. During development of the site, everything was working as it should using HTTP on a test url (test.site.com). However after I installed the SSL on the webserver and ISA array members, and published the site (www.site.com), a page running AJAX scripts was not able to run the scripts properly on HTTP. The stranger thing is that the scripts run properly on HTTPS.
The error on IE when using HTTP shows the following:
This error is not present when using HTTPS, and since the same instance of the site in IIS is being used (the only thing we did to bring the site live is to change the web publishing rules from the testing rule to the production rule with SSL), I am thinking this error is caused somewhere in the web publishing rule config.
Here is my config for the publishing rule:
Allow From Anywhere To www.site.com Server IP 10.10.9.51 Check Forward original host name instead of actual one (specified in the Internal site name field) Requests appear to come from ISA server computer Traffic HTTP HTTPS Public name Requests for the following Web sites: www.site.com Path External same as Internal /* Authentication: No delegation and client cannot authenticate directly Bridging: Redirect to Http port 80 and Redirect to Https port 443 checked Users: Everyone Schedule: Always
Web Listener Config: Network: External VIP of ISA array member Connections: Enable HTTP connections on port 80 and Enable HTTPS connections on port 443 checked Http to Https redirection: Do not redirect traffic from HTTP to HTTPS Certificates: Use a single certificate for this Web Listener www.site.com No Authentication Nothing configured for Forms and SSO tabs.
The settings I have posted here are similar to settings I used for publishing the test site, bar those that involve HTTPS. Everything else is the same, and all the pages work properly. It also does not make sense that the page does not work for HTTP but works for HTTPS. Does anyone have any idea, or does the problem not lie with ISA at all?
Update: Ok I just tested the site internally and the page works in HTTP perfectly, so the problem has got to be with the publishing rule config somewhere.
< Message edited by bingyeo -- 25.Jan.2010 2:19:02 AM >