Thanks for your prompt reply. I appreciate the rapid feed back.
That eliminates that possible cause.
I will now continue to check with my broadband supplier to resolve the issue.
Have a great day when you wake.
Kind regards JohnL.
···
From: sailwave@yahoogroups.com [mailto:sailwave@yahoogroups.com]
Sent: 07 September 2017 10:49
To: sailwave@yahoogroups.com
Subject: Re: [sailwave] This site is unsafe
I think I may have it working for all browsers now.
Lesson is don’t believe what you read on Google - work it out yourself!
Let me know - getting a little late now will test it again in the morning
Jon
Jon Eskdale
07530 112233
Skype “eskdale”
On 6 September 2017 at 23:11, ‘john’ jladewig@tpg.com.au [sailwave] sailwave@yahoogroups.com wrote:
Hi Jon,
I am having trouble uploading my results . I first experienced this on Sunday night Australian time.
Do I need to change the destination server to https://www.sailwve.com, and the base URL to https://www.sailwave.com/results?
I also changed from copper to the Australian NBN during the previous week.
Thanking you for your assistance.
Kind regards John
From: sailwave@yahoogroups.com [mailto:sailwave@yahoogroups.com]
Sent: 07 September 2017 4:35
To: sailwave@yahoogroups.com
Subject: Re: [sailwave] This site is unsafe
Hi Jorgen,
This comes about as the Sailwave site has now been upgraded to https (as per the announcement on the Sailwave.com website) as required by the major browsers and Google who have announced that they will be warning that sites are unsafe from next month if they accept input of data but the site is not using https. So we have upgraded the Sailwave site to https
clicking on your link http://sailwave.com/results/Kerteminde/ks-rr-2017-result.html actually works fine for me using Chrome as it automatically adds the www and becomes https://www.sailwave.com/results/Kerteminde/ks-rr-2017-result.html. So no problem if they use Chrome
The link is safe so they could ignore it but the best solution is to add the www
and use then address https://www.sailwave.com/results/Kerteminde/ks-rr-2017-result.html
If you use http: the site will automatically redirect to https: so you can use either.
The next version of Sailwave will have the https://www. to replace the http:// in its link to publish
Hope that helps
Jon
Jon Eskdale
07530 112233
Skype “eskdale”
On 6 September 2017 at 18:59, Jørgen Holm jorgen@dyrberg-holm.dk [sailwave] sailwave@yahoogroups.com wrote:
I have used sailwave and posting results at the sailwave file. No problems until recently when I (and other) receive at unsafe message from EDGE and other browsers looking at the resultfile. (ex https://sailwave.com/results/Kerteminde/ks-rr-2017-result.html )
Details in the message is
Hostname in certificate for website fdiffers from the website you are visiting
Errorcode : DLG_FLAGS_SEC_CERT_CN_INVALID
Continue to website (Not recommended)
The message disappear if the web-URL (sailwave generated) is modified to https://www.sailwave.com/results/Kerteminde/ks-rr-2017-result.html
As far as I can se from the documentation I cannot change the link generated by Sailwave ( message : Page uploaded to Sailwave. You can publicise the page using this address:-
http://sailwave.com/results/Kerteminde/ks-rr-2017-result.html )
What is the correct action
1 : Use adress http://www.sailwave.com/results/Kerteminde/ks-rr-2017-result.html instead of http://sailwave.com/results/Kerteminde/ks-rr-2017-result.html
2: tell the users to ignore the warning
3: any setup change in sailwave
The problem with solution 1 is, that we have several result-links in different regattas, so it is a lot of work to modofy homesites Iin html alink ref=xxxx
Best Regards
Jørgen’Kerteminde Sejlklub
