Hi,
I recently changed the .htaccess file so that my site shows up as https however now when anyone clicks to but something from the site they hat a Security Warning about the insecure connection.
I guess it’s because in the Code the link to Mac E Commerce is http: but does anyone know how I can modify it to https ?
Thanks in advance
Mark
freewaytalk mailing list
email@hidden
Update your subscriptions at:
The Action that creates this URL is bundled into the Freeway application itself, and is encoded so it cannot be updated by outsiders. Softpress will need to issue an update in order to fix this.
I could try writing an add-on Action that would locate these “www.aitsafe.com” URLs and rewrite their protocol, but I don’t know if Mals uses the same hostname for secure as they do for non-secure connections, and I’m not clear whether I could get my Action to fire at the correct stage of publishing in order to override these links. Because the Action is encoded, I can’t read it and see which publishing “stage” I would need to set my Action in. I was able to make the HTTPS CDN Helper because I was overriding Actions I had written myself, and could read and inspect.
Walter
On Nov 8, 2018, at 4:45 AM, M Lewis email@hidden wrote:
Hi,
I recently changed the .htaccess file so that my site shows up as https however now when anyone clicks to but something from the site they hat a Security Warning about the insecure connection.
I guess it’s because in the Code the link to Mac E Commerce is http: but does anyone know how I can modify it to https ?
Thanks in advance
Mark
freewaytalk mailing list
email@hidden
Update your subscriptions at:
Information for existing FreewayTalk / Groups.io users - Site Feedback - Softpress Talk
freewaytalk mailing list
email@hidden
Update your subscriptions at:
https://freewaytalk.softpress.com/person/options
Stabbing in the dark, I made this:
http://actionsforge.com/actions/https-helper
Please apply it to each page that hosts a Mals Cart, and let me know if this is enough to fix the problem for you. I hope so, since Jeremy has his hands full converting Freeway to 64-bit.
Walter
On Nov 8, 2018, at 7:24 AM, Walter Lee Davis email@hidden wrote:
The Action that creates this URL is bundled into the Freeway application itself, and is encoded so it cannot be updated by outsiders. Softpress will need to issue an update in order to fix this.
I could try writing an add-on Action that would locate these “www.aitsafe.com” URLs and rewrite their protocol, but I don’t know if Mals uses the same hostname for secure as they do for non-secure connections, and I’m not clear whether I could get my Action to fire at the correct stage of publishing in order to override these links. Because the Action is encoded, I can’t read it and see which publishing “stage” I would need to set my Action in. I was able to make the HTTPS CDN Helper because I was overriding Actions I had written myself, and could read and inspect.
Walter
On Nov 8, 2018, at 4:45 AM, M Lewis email@hidden wrote:
Hi,
I recently changed the .htaccess file so that my site shows up as https however now when anyone clicks to but something from the site they hat a Security Warning about the insecure connection.
I guess it’s because in the Code the link to Mac E Commerce is http: but does anyone know how I can modify it to https ?
Thanks in advance
Mark
freewaytalk mailing list
email@hidden
Update your subscriptions at:
Information for existing FreewayTalk / Groups.io users - Site Feedback - Softpress Talk
freewaytalk mailing list
email@hidden
Update your subscriptions at:
Information for existing FreewayTalk / Groups.io users - Site Feedback - Softpress Talk
freewaytalk mailing list
email@hidden
Update your subscriptions at:
https://freewaytalk.softpress.com/person/options
Hi Walter,
Thanks for this info. I applied the HTTPS Helper to the affected pages and it has resolved the issue.
Thanks again.
Mark
freewaytalk mailing list
email@hidden
Update your subscriptions at:
Hiya, where would i need to put this in order for it to work on my site as I am having a similar issue
It’s a page action. You apply it to the page, and make sure that the “Use HTTPS everywhere” checkbox is checked.
To apply a page action, first make sure that nothing on the page is currently selected. (Click somewhere blank on the pasteboard outside of the visible page.) Then from the Actions menu, choose the HTTPS Helper option. That’s going to put its control panel into the Actions palette (so make that visible if you don’t have it always open), and the checkbox is on by default. If you’ve already applied the action to the page, then (when nothing is selected on the page) it will show a tab in the Actions palette, and you can click that to bring it forward.
When you publish, the action loops through the page code and rewrites any URLs that begin with http:// to https://. That’s it.
Note that it only does this to URLs in actual Freeway-generated tags: links, scripts, a tags (linking from one page to another), and form tags. If you have done something else in your page, perhaps by using one or another of the Extended interfaces to enter hand-written JavaScript or whatever, those URLs will be ignored by the Action. But if you added them that way, you can also find and edit them the same way.
The checkbox in the interface is useful for local testing. If you are using Freeway’s Preview in browser feature, you will very likely find that scripts won’t load from https URLs in the same context as a file:/// URL for the surrounding page, and thus you can’t debug your effects.
Hope this helps!
Walter
PS: You may want to apply this Action to a master page so you don’t need to add and adjust it on each page in your site. All I can say about that is check carefully through your site if you do that. You may find that the link between master page Actions and the child pages based on them can become “iffy”. Repairing that broken link can be difficult to do, leading to a lot of clicking around and removing and re-applying Actions on individual pages. If you have more “regular” pages in your site than Mals pages, you may want to stick to a page-at-a-time approach. But if you have a “view cart” link on every page, then you will definitely want to do this on every page, since those won’t work correctly without the https protocol.