I am managing some sites that dont have their own SSL certificates, and I am accessing them through a subfolder on the main domain of the hosting service, using the main domain name of that hosting account, which does have SSL, so that I can secure my logins.

For admin tasks in particular, but generally speaking, really; on such sites that are merely information to the public with no active users logging in, other than myself and other admins, we do not want to log in through the non-SSL URL (the site of the add-on domain), as that has security implications such as exposing the cookie etc.

However: when wanting to push a new content node to Twitter, and using !title - !url as the pattern, those tweets automatically get the current path of the main domain including the subfolder, and not the site domain.

This is confusing for people seeing a URL that does not correspond to the domain that is visible in the Twitter profile info. Simply bad.

The only way to get around it, seems to be logging in insecurely on the normail site domain (non-SSL), which is even worse...

It would be very practical to be able to specify something like "!title - /!path" instead of !title - !url, so that I can manually put the site domain there instead of getting the "https://maindomain.com/subfolder".

PS. such a solution should let us specify the http (or httpS) with/without the www part on the pattern setting. That should not be fetched from the current browser session window unless it is NOT specified on that settings line.

Comments

Leeteq created an issue. See original summary.

damienmckenna’s picture

Status: Active » Closed (duplicate)

There's an existing issue for adding this functionality: #793458: Post links to http rather than https URLs