Answered by:
managed paths and https

Question
-
Hi!
I am currently building an intranet portal with SharePoint 2010. One feature I am using is the My Sites feature.
Therefore I created a new Site Collection in an explicit managed path: "my"
...and added a wildcard managed path "my/personal"
within the "parent" web application (port 80).The "My Sites" feature works well, as long as I use http:
http://myservername and http://myservername/my works fine.
However I also want to provide a secure HTTPS connection. Therefore I went into the IIS Administration, created a "self-signed certificate" and added a binding to the mentioned web-application, which uses "https" and that certificate.
When I now connect to https://myservername everything still works, along with the expected security warning, as the certificate is unknown to internet explorer. ;)
However I CANNOT connect to https://myservername/my
I also added another eplicit managed path along with a site collection for team foundation server 2010 integration which also only works via "http" and not with "https"
Therefore I believe, that I have to configure something additional, so MOSS 2010 can work with the managed paths in https?
Any help would be appreciated!!!!
Thanks! :)
Wednesday, May 5, 2010 9:59 AM
Answers
-
You may need to add an alternate access mapping for HTTPS, that's fixed similar problems for me.
- Marked as answer by Gentledepp Thursday, May 6, 2010 6:41 AM
Wednesday, May 5, 2010 4:58 PM
All replies
-
Hi!
Another strange thing about these managed paths:
They work in the browser as long as the local computer name is entered as servername:
but as soon as i use its ip address, or the term "localhost" the browser states that it cannot find the website:
however, using http://localhost or https://localhost to access the base site collection works fine.
What is going wrong here?!?!?!?!
Wednesday, May 5, 2010 2:51 PM -
You may need to add an alternate access mapping for HTTPS, that's fixed similar problems for me.
- Marked as answer by Gentledepp Thursday, May 6, 2010 6:41 AM
Wednesday, May 5, 2010 4:58 PM -
Hey DallasRoseBoston - you're great! :)
I simply went into the sharepoint central administration, selected my web application and clicked "managed alternate access mappings".
There I clicked on "Edit public URLs" and added the following:
Default: http:/ /myservername
Intranet: http:/ /theNameTheServerHasInDNS
Extranet: https:/ /theNameTheServerHasInDNS
Now everything works fine! Thank you very much!!! :)
Thursday, May 6, 2010 6:41 AM