SSL breaks custom URLs

[brightroamer]

Hi all,

:: AC info
AbleCommerce for ASP.NET
VERSION: 7.0.7.14600
No direct public link available to the website in question

:: Issue
When SSL mode is in effect (navigating within account pages), custom URLs such as "/Business-Roaming.aspx" break into "/Layouts/Webpages/NoSidebars.aspx?WebpageId=6".
Same holds true for category pages and for the product pages as well.

While SSL mode is inactive (navigating outside of account and checkout pages), the URLs to ( content | categories | products ) resolve into custom URLs as defined in ( Page URL | Custom URL | Custom URL ) respectively.

URL in example is called as:

Code: Select all

<a href="~/Business-Roaming.aspx">For Business</a>

For a brief moment I can see "https://www.domain.com/Business-Roaming.aspx" appear in the address bar, just to be replaced with http://www.domain.com/Layouts/Webpages/ ... ebpageId=6 when page is finally served.

Is this a known issue? The only potential workaround I see is to hard-code every link to non-secure pages to start with "http://", to hopefully bypass the redirect from SSL to regular protocol, as that's when the problem seems to rise. I would like to retain the flexibility of being able to write relative URLs.

Thank you in advance for any suggestions.

[jmestep]

I had seen that on a site myself and then when I went back to try to find it, it didn't happen. I must have been in SSL mode the first time.
Is there a reason why you are accessing it via https ?

[brightroamer]

Thank you for reply Judy.

I suppose I do not need the content and product pages to be accessible via https, however:

1. When a visitor clicks on Business-Roaming.aspx link while browsing his/her account pages, the system will form a https://www.domain.com/Business-Roaming.aspx URL, because SSL mode is mandatory for all in-account and checkout pages, and all relative links on page are treated as links to secure pages -- OK;
2. Content pages have no sufficient reason to be served over SSL, thus, the AbleCommerce redirects them to http instead -- OK;
3. The AbleCommerce now looks up custom URL in the database and locates the intended end-point page -- OK;
4. AbleCommerce constructs the raw URL to the object http://www.domain.com/Layouts/Webpages/NoSidebars.aspx?WebpageId=6 , ignoring custom URL specified in product | category | content page configuration -- BUG!

Spitting out raw URL constructs defeats the purpose of having the ability to specify custom URL for SEO and other aesthetic reasons...