SSL / Host headers

TheMSsForum.com: The Microsoft Software Forum

I had a support case reguarding this issue for a few weeks and the short story is there is no way around this as SharePoint (it's a WSS issue, not SPS, but because SPS leverages WSS, it's an issue with SPS as well) doesn't support IP-bound virtual servers AND even if you put an ISA Server in front of the SharePoint box, it won't help as WSS doesn't support SSL Termination… only SSL bridging.

You can run additional sites off additional ports, but that's not a clean or viable option for everyone (but it ~will~ work). I understand WSS SP2 will fix this as it was one of the most requested "features" to be addressed in 2004 by MS SharePoint customers.

-AC

www.andrewconnell.com

nntp://msnews.microsoft.com/microsoft.public.sharepoint.windowsservices/<u6f0LGc$EHA.1408@TK2MSFTNGP10.phx.gbl>

Does anyone know of a way to work around "IP-bound virtual servers are not
supported in SharePoint Portal Server 2003 or in Windows SharePoint
Services"? The post at
http://support.microsoft.com/default.aspx?scid=kb;en-us;830342 suggests that
host headers are a "workaround" but host headers don't function under HTTPS,
so we cannot use "all unassigned." Any help appreciated.

There is a suggestion that registering Web Parts into the GAC is one method
of circumventing the problem, but I am having issues with the Public Key
being different on the dev box where I build the WP and the production
environment (where the IP-bound site lives). Has anyone utilized this fix?





[microsoft.public.sharepoint.windowsservices]
Top

Re: SSL / Host headers by Jeremy

Jeremy
Fri Mar 18 07:32:32 CST 2005

I am a little confused by your posting. I run a WSS site using host headers
and it works just fine. In fact I have about 7 web sites running on the
same server all bound to the same IP on port 80. If it is a specific
problem using SSL, I may be of no help since none of my sites are using SSL,
but if it is just a case of getting multiple sites to use the same IP on
port 80 I think I might be able to help you out.

Jeremy

"AC" <swamplander@NOSPAMgmail.com> wrote in message
news:O2sc146KFHA.2860@TK2MSFTNGP10.phx.gbl...
> I had a support case reguarding this issue for a few weeks and the short
> story is there is no way around this as SharePoint (it's a WSS issue, not
> SPS, but because SPS leverages WSS, it's an issue with SPS as well)
> doesn't support IP-bound virtual servers AND even if you put an ISA Server
> in front of the SharePoint box, it won't help as WSS doesn't support SSL
> Termination&hellip; only SSL bridging.
>
> You can run additional sites off additional ports, but that's not a clean
> or viable option for everyone (but it ~will~ work). I understand WSS SP2
> will fix this as it was one of the most requested "features" to be
> addressed in 2004 by MS SharePoint customers.
>
> -AC
>
> www.andrewconnell.com
>
>
> nntp://msnews.microsoft.com/microsoft.public.sharepoint.windowsservices/<u6f0LGc$EHA.1408@TK2MSFTNGP10.phx.gbl>
>
> Does anyone know of a way to work around "IP-bound virtual servers are
> not
> supported in SharePoint Portal Server 2003 or in Windows SharePoint
> Services"? The post at
> http://support.microsoft.com/default.aspx?scid=kb;en-us;830342 suggests
> that
> host headers are a "workaround" but host headers don't function under
> HTTPS,
> so we cannot use "all unassigned." Any help appreciated.
>
> There is a suggestion that registering Web Parts into the GAC is one
> method
> of circumventing the problem, but I am having issues with the Public Key
> being different on the dev box where I build the WP and the production
> environment (where the IP-bound site lives). Has anyone utilized this fix?
>
>
>
>
>
> [microsoft.public.sharepoint.windowsservices]
>
>


Top