Cloudflare, Ancestry, and Rootsweb addresses
Genealogy
the Rootsweb addresses to use https. Currently rootsweb address are
http://rootsweb.com. My address is "http://homepages.rootsweb.com ›
~bdweisel"
Most sites are now encrypted and use https. Ancestry should correct this.
Bonnie
HTTPS is HTTP with encryption and verification. The only difference
between the two protocols is that HTTPS uses TLS (SSL) to encrypt normal
HTTP requests and responses, and to digitally sign those requests and
responses. As a result, HTTPS is far more secure than HTTP. A website
that uses HTTP has http:// in its URL, while a website that uses HTTPS
has https://.
Pat Asher
Pat Asher
Dave Naylor
There is nothing wrong with Ancestry or RootsWeb.
The problem is that many users are still using http: to access their pages instead of the secure https:
Check *all* your links and bookmarked pages to ensure that you don't have any http: addresses for RootsWeb pages. If you have any change them to https:
Do not refer anyone to an http: address if at has a usable https: alternative.
Most RootsWeb user pages are best accessed by using the https://sites.rootsweb.com/ prefix. If you're not using it then check it to see if it works for your pages.
Cheers! -- Dave
delorw...@gmail.com
All of the addresses now show that when visiting the sites, apparently except when someone doesn't use the correct addresses.
There's nothing wrong with the addresses, it's the users.
Deloris Williams
Pat Asher
However -- I have to use MS Edge to access images of source material from familysearch.org
They don't make life easy, do they? lol
Pat Asher
Hi Pat,
Thanks for the update. This is getting very interesting. This is the link for a page that I had up yesterday on Firefox browser.
http://homepages.rootsweb.com/~bdweisel/GeoMichael/Frederick-Wiseley.html
Attaching a screen shot for what I see on my browser.
But when I put the link into Microsoft Edge browser (Windows 10) , the page comes up but it is also http and not https!!! 2nd attachment. The link also works normal on my iPad Chrome browser.
So clearly the problem is on my end. My provider is spectrum.net. But for now will use Edge until the problem resolves itself.
thanks, Bonnie
--
Website FAQs: http://sites.rootsweb.com/~gearyfamily/rootsweb-hosted-web-sites.html
FTP FAQs: http://sites.rootsweb.com/~gearyfamily/publishing-your-sites.html
To contact the owners of this group, write to rw-website-...@googlegroups.com
---
You received this message because you are subscribed to the Google Groups "RootsWeb-Website-Help" group.
To unsubscribe from this group and stop receiving emails from it, send an email to rw-website-he...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/rw-website-help/211d54bb-6bcf-519f-58e8-ae53ebc03434%40att.net.
Hotrum
Genealogy
Greetings All,
Apparently it's my Firefox and the Google search engine. Even
though I tried to remove from history and bookmarks all references
to Weisel, Rootsweb, Ancestors it was not a fix and I didn't feel
like deleting all the history.
I did have Google Chrome installed with bookmarks (but with little history) and it was using the Yahoo secure search engine. Searches on Rootsweb sites were OK, Chrome/Yahoo was using https:// addresses.
Set Firefox to use the Yahoo search engine but result was still http:// and Cloudflare page.
Why I just started getting the Cloudflare blocks today is still an unknown. But for now will start using Chrome instead of Firefox.
-Bonnie (Thanks for the replies and support)
Here is what Google had to say when clicking on the ": "
About this result
Source
homepages.rootsweb.com was first indexed by Google more than 10
years ago
· http://homepages.rootsweb.com/~bdweisel/
· Your connection to this site is not secure
More about this page
Not personalized
This result isn't personalized based on Google activity from this
browser. Learn more
Manage your data in Search
Your search & this result
· These search terms appear in the result: weisel and
ancestors
· A term related to your search appears in the result:
genealogy
· The result is in English
· This result seems relevant for searches from many regions,
including the United States
Learn more search tips
This is a search result, not an ad. Only ads are paid, and they'll
always be labeled with "Sponsored" or "Ad."
--
Website FAQs: http://sites.rootsweb.com/~gearyfamily/rootsweb-hosted-web-sites.html
FTP FAQs: http://sites.rootsweb.com/~gearyfamily/publishing-your-sites.html
To contact the owners of this group, write to rw-website-...@googlegroups.com
---
You received this message because you are subscribed to the Google Groups "RootsWeb-Website-Help" group.
To unsubscribe from this group and stop receiving emails from it, send an email to rw-website-he...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/rw-website-help/f215451b-12fc-df1f-bce6-7edb45439fb6%40yahoo.ca.
Barry Carlson
Just be aware, the RW server has a permanent redirect in place, which
means that all requests will result in an https:// output. In the case
of Freepages, the expected input must be formatted as follows:-
freepages.rootsweb.com/~account/nominated directory, e.g.
genealogy/page-name.html (or optionally nothing if the directory has an
index.html page)
In the case of the "gearyfamily" links, they haven't been updated to
https:// and there is absolutely no security risk involved, as the
server automatically provides the 'redirect'.
Barry
-------------------
Dave Naylor
I was aware of the redirect that's in place. However, requests have to reach the RW servers for that to take affect. The blocking that is occurring is *before* requests get to RW.
The expected input for Freepages is not limited to what you stated as anyone trying (and using) the better alternatives will discover.
I did not say there was any "security risk" in the use of http:// links. The problem with them, as stated above, is that redirects only function after the request reaches RW servers.
Cheers! -- Dave
Pat Geary
pat g