https instead of http

[harryd]

Does Web Designer know about using "https" instead of "http" and does doing that present any problems. For instance, when adding a link, the program corrects www.abc.com to http://www.abc.com. Can that be changed so that it defaults to https?

[gwpriester]

No. To be able to use https:// the site must have a SSL certificate.

From my web host's C-Panel

The SSL/TLS Manager will allow you to generate SSL certificates, certificate signing requests, and private keys. These are all parts of using SSL to secure your website. SSL allows you to secure pages on your site so that information such as logins, credit card numbers, etc are sent encrypted instead of plain text. It is important to secure your site’s login areas, shopping areas, and other pages where sensitive information could be sent over the web.

[gwpriester]

And I should point out, like domain names, SSL certificates cost money and need to be renewed each year. Unless you require a secured link, for example you have a blog or are making sales from your site, you probably do not need a SSL certificate.

[harryd]

And I should point out, like domain names, SSL certificates cost money and need to be renewed each year. Unless you require a secured link, for example you have a blog or are making sales from your site, you probably do not need a SSL certificate.

I do have an SSL certificate and I do plan to use https. I'm asking what is the compatibly of Web Designer with https?

[siran]

That is not a matter of Xara. Xara creates static files that don't care if they are transferred via http or https.
If you are worried clicking an internal link might be broken when the page is opened via https you don't need to be. All internal links are releative and retain the protocol.
I don't think you can change the default of the automatic address correction to https. But that should not be a big problem. You should provide it anyway because http://xyz might reference a completely different site than https://xyz

[sculptex]

As siran says, the internal URL links generated by xara are relative, so index.htm links to aboutus.htm not http://www.xyz.com/aboutus.htm so if you visit https://www.xyz.index.htm the https is preserved.

However, if you visit your pages on https and they include images or widgets etc. that are from non-https sites you will get browser warnings, so make sure you haven't got any of those.

Once you are happy that's okay, you need to set about making incoming links https.
First, update the sitemap to use HTTPS instead of http.
If you are signed up to Google search console, you can submit your new sitemap in there.
Then, if you are on an apache server, you can update your .htaccess file to permanently redirect all pages to HTTPS automatically. There are various posts on the internet but I can post code here if you like.
Its best to do sitemap and not to just rely on htaccess method as otherwise each initial page load would still require a redirect and Google frowns upon this!

[harryd]

Thanks sculptex, that was very helpful. I'll get back to you later if I have questions.

[Acorn]

Above the Link box, check that the Correct automatically box is unticked.
Then enter the https//:<external_url> in full. For the others, Xara knows where it is.

Acorn

[RKissane]

Gary,

https://letsencrypt.org/ is very interesting and is free. The only thing is it is designed for servers that are Linux based so sites on windows servers would have to go the traditional routes for the SSL Certificates.

Ray

[Acorn]

Gary,

https://letsencrypt.org/ is very interesting and is free. The only thing is it is designed for servers that are Linux based so sites on windows servers would have to go the traditional routes for the SSL Certificates.

Ray

Ray, have you got any example sites you have used with this SSL provider?

Acorn