Hi,

Try adding this to your user.config

<add key="ResolveFullUrlsForMenuItemProtocolDifferences" value="true" />

then touch Web.config to make it reload settings.

Hope it helps,

Joe

I just tried it on my machine and I cannot produce the problem and reviewing the code it is definitely not redirecting to the unfriendly url.

I think you must have something else doing that redirection like IIS url re-writer or some other IIS module or custom code.

Hope it helps,

Joe

I don't see how iframes on the page could have anything to do with it. Possibly some configuration difference, but I need more information to produce the problem since I'm not seeing it. 

I would try different skins and see if that has any effect on the problem and please tell me as much as possible about the installation like is it a root site or sub folder, using multi sites or not, using .NET 3.5 or .NET 4.

If you can identify steps to produce the problem I will treat it as a bug, but otherwise I think there are factors on your installation such as IIS modules or something else involved. Nothing has changed about the SSL support in a long time and no-one else has ever reported having this problem.

Given all your previous questions it seem likely that you are using custom code and produced your own build regardless of whether the page in question has any custom features on it.

Best,

Joe

The setting would only work if using the built in menus. All it does is use the fully qualified url with https for links to secure pages to avoid the ssl redirect completely. You could try the same with your hard coded links, for the secure pages hard code it with https://yoururl.

Many of the included skins in mojoportal illustrate split menus. Typically a top level menu <portal:SiteMenu and then a different menu for child pages <portal:PageMenu. Some, like the adreasvicklund-02 and -alt1 illustrate 2 or more levels of horizontal menus then finally a vertical menu for pages below those levels. Seems like you could do that instead of the image map you are using.

It is not obvious the menu structure in some skins until you create a bunch of pages in hierarchy that shows them, since menus are only shown if they have pages at their level.

Hope it helps,

Joe

Seems like you could arrange the hierarchy as needed to fit the desired menu structure, but if not, you could create additional pages at the needed level and then set the url for the page to the fully qualified url (with http:// or https:// not ~/someurl) of the target page (that lives at a different level) the same as if you were linking to a different site.

Hope it helps,

Joe