Editing the site under a shared SSL domain

This is the place to report bugs and get support. When posting in this forum, please always provide as much detail as possible.

Please do not report problems with a custom build or custom code in this forum. If you are producing your own build from the source code and have problems or questions, ask in the developer forum, do not report it as a bug.

This is the place to report bugs and get support

When posting in this forum, please try to provide as many relevant details as possible. Particularly the following:

  • What operating system were you running when the bug appeared?
  • What database platform is your site using?
  • What version of mojoPortal are you running?
  • What version of .NET do you use?
  • What steps are necessary to reproduce the issue? Compare expected results vs actual results.
Please do not report problems with a custom build or custom code in this forum. If you are producing your own build from the source code and have problems or questions, ask in the developer forum.
This thread is closed to new posts. You must sign in to post in the forums.
1/18/2015 5:34:28 AM
Gravatar
Total Posts 8

Editing the site under a shared SSL domain

If I edit the site under a shared SSL domain, for example https://site3.sslhosting.com/mysite_com/Admin/PageTree.aspx as follows:

1. Add a New Page with a link to the same site, for example 'http://www.mysite.com/test.aspx?param=p1'

2. Click OK

The link will be displayed in the menu only if you visit the site as   https://site3.sslhosting.com/mysite_com/

If you visit it as usually via  http://www.mysite.com/  - the link will not be displayed no matter if the user is authenticated or not.

1/18/2015 7:37:14 AM
Gravatar
Total Posts 18444

Re: Editing the site under a shared SSL domain

yeah, the sitemap is cached by the runtime, you have 2 different web sites that point to the same set of files and database, the one that adds or removes a page can clear its own cache but it can't clear the cache of the other site, so the change won't be seen on the other site until its own cache is cleared or expires

bottom line: shared ssl is problematic for many reasons, we think it is a very bad solution, we don't support it and we recommend don't use it.

my best advice for you is get a real ssl certificate for your own domain and don't try to use shared ssl

You must sign in to post in the forums. This thread is closed to new posts.