Wikipedia:Link rot/URL change requests/Archives/2022/June
 | This is an archive of past discussions about Wikipedia:Link rot. Do not edit the contents of this page. If you wish to start a new discussion or revive an old one, please do so on the current main page. |
reports.iihf.hockey/Hydra
When I try to open this website, my Firefox warns me that there is a potential security risk. And there are hundreds of such websites in Wikipedia articles. For example, click on this link: https://reports.iihf.hockey/Hydra/2/ Do you see that? So I need a bot that can edit the following string:
- https://reports.iihf.hockey/Hydra
Note: There are also URLs with "http" instead of "https" and also with "hydra" (lower-case "h") instead of "Hydra":
- http://reports.iihf.hockey/Hydra
- http://reports.iihf.hockey/hydra
The correct URL without warning is this:
- https://stats.iihf.com/Hydra
For example, https://stats.iihf.com/Hydra/2/
Thank you in advance. Maiō T. (talk) 21:12, 29 May 2022 (UTC)
- User:Maiō T. I think the problem is https vs. http .. compare: https://reports.iihf.hockey/Hydra/2/ (broken) and http://reports.iihf.hockey/Hydra/2/ (works) .. it looks like https://stats.iihf.com/Hydra/2/ returns the same content. So either convert to http, or convert to the new domain iihf.com .. the least disruptive option is convert to http for all links at reports.iihf.hockey -- GreenC 15:05, 30 May 2022 (UTC)
I went ahead and fixed them by changing to http. It edit 700 articles and modified 2,646 URLs plus some other fixes like removing {{dead link}} tags, switching |url-status=dead to live, etc. If you see any problem let me know! -- GreenC 17:30, 30 May 2022 (UTC)
- @GreenC: Oh no, I'm late. I like the https more. It's more modern. Over time, both Google and Mozilla (creator of Firefox) plan on depreciating "http" - I read on the internet today. :( Maiō T. (talk) 18:30, 30 May 2022 (UTC)
- HTTPS mean the connection is secure, it uses TLS/SSL encryption. The website (not the browser) needs have TSL/SSL otherwise it must use HTTP. HTTPS is purely optional for websites, many support it, many don't. It requires paying a yearly fee. Many website ssupport it at one time, then stop because they stop paying the fee for whatever reason. It is not correct that Google and Mozilla will deprecate http, not sure where you read that. -- GreenC 18:53, 30 May 2022 (UTC)
- @GreenC: Okay. For now, it could stay with http. But I'll ping you in a year or two if it doesn't work. ;) Regards, Maiō T. (talk) 19:20, 30 May 2022 (UTC)
- When I edit ice hockey articles, I always use the "https://stats.iihf.com" references. So I was disappointed and a little angry yesterday. However, today I realize that fixing 2,600 dead links was a pretty good job. So thanks. Maiō T. (talk) 10:41, 31 May 2022 (UTC)
- OK glad things are working now. Basically the http vs https has a reason and the site has to support the https protocol otherwise it will return that error. -- GreenC 15:30, 31 May 2022 (UTC)
- When I edit ice hockey articles, I always use the "https://stats.iihf.com" references. So I was disappointed and a little angry yesterday. However, today I realize that fixing 2,600 dead links was a pretty good job. So thanks. Maiō T. (talk) 10:41, 31 May 2022 (UTC)
- @GreenC: Okay. For now, it could stay with http. But I'll ping you in a year or two if it doesn't work. ;) Regards, Maiō T. (talk) 19:20, 30 May 2022 (UTC)
- HTTPS mean the connection is secure, it uses TLS/SSL encryption. The website (not the browser) needs have TSL/SSL otherwise it must use HTTP. HTTPS is purely optional for websites, many support it, many don't. It requires paying a yearly fee. Many website ssupport it at one time, then stop because they stop paying the fee for whatever reason. It is not correct that Google and Mozilla will deprecate http, not sure where you read that. -- GreenC 18:53, 30 May 2022 (UTC)
- @GreenC: Oh no, I'm late. I like the https more. It's more modern. Over time, both Google and Mozilla (creator of Firefox) plan on depreciating "http" - I read on the internet today. :( Maiō T. (talk) 18:30, 30 May 2022 (UTC)
apps.dtic.mil
Many links to apps.dtic.mil are currently broken. Jarble (talk) 21:57, 28 May 2022 (UTC)
- Jarble: *.dtic.mil has about 29 sub-domains including apps. All but 3 are functionally dead for example returns PR_CONNECT_RESET_ERROR (Firefox). On Chrome it's "ERR_CONNECTION_RESET". Tried on multiple computers. I assume it is similar for everyone a military firewall. I thought maybe the URLs had moved but nope, check this index page and the URL to the first entry is apps.dtic.mil so the URLs have not changed location. Fortunately Wayback has saved most of the links, mostly PDF documents, before the firewall - which if the case was pretty recent past couple years. I believe they should be considered dead links and archives added. Working... -- GreenC 05:28, 31 May 2022 (UTC)
This took 3 full days of work and multiple bot reiterations and passes. The site has internal problems that needed to be discovered and programmed for. The data on-wiki was also pretty inconsistent. As such I can't say for certain how many citations were modified but it was at least 5,000 and that many pages edited. It was able to save a lot of links by moving dead URLs to a new URL structure. There is no doubt some unknown problems still in the data, and more links that might be saved through moves. Anyway I've done a lot and need to move on.
Resolved