Web Publishing Problem, Any Help Appreciated!!

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

I have a two server network; both MS Windows 2003 SP1. My main server runs
ISA 2004 and Exchange 2003, and the second server is joined as a member
server and hosts my website and Certificate server. I set up OWA publishing
and configured the site to use ssl. Works like a champ. The second publishing
rule forwards my website traffic to my second server. I configured it as a
straight http connection, but when external users connect they get an error
message unless they access it as https. I can't figure out why it would
require https on the second server. They both use the same listener, but the
listener is configured to allow both http and https traffic. The website is
accessable internally as http. I would prefer that OWA be https and the
website be http, but in a pinch I would settle for automatically redirecting
http traffic to my website as https. Any help would be appreciated.
.

Relevant Pages

  • Bad Request (Invalid HostName)
    ... I have a website at "http://domainXPTO.net"; ... following one AND ONLY ONE sucessfull call to any WebMethod. ... All other direct HTTP calls or WebMethod calls return: ... and SQL Server database) and everything works fine. ...
    (microsoft.public.dotnet.framework.compactframework)
  • Re: Change Website from File to Http
    ... What is the Server 2003, a QA Server or Production Server? ... publishing the website for QA or Production just use the Publish Website ... Now we want to change it to an HTTP site. ...
    (microsoft.public.dotnet.framework.aspnet)
  • HTTP site published as HTTPS
    ... server and hosts my website and Certificate server. ... I set up OWA publishing ... rule forwards my website traffic to my second server. ... listener is configured to allow both http and https traffic. ...
    (microsoft.public.isa.publishing)
  • Re: Accidently imported a web site to http://localhost
    ... If the live/remote server doesn't have the FP extensions, then you can not use http, you have to use ... > choice I have is to pick HTTP, because the server that the web site runs on ... > 2) On my laptop which I messed up by creating a FP website at http://localhost ...
    (microsoft.public.frontpage.client)
  • RE: Outlook RPC over HTTp deosnt work
    ... try to use RPC over HTTP to connect the Exchange Server. ... What SBS is running on the problematic Server? ...
    (microsoft.public.windows.server.sbs)