Benutzer Diskussion:Frog23/Dead Link Finder/en

aus Wikipedia, der freien Enzyklopädie
Zur Navigation springen Zur Suche springen

[XX1] (Could Not Reach Server) error even though server is available[Quelltext bearbeiten]

Hello,

I just started using your dead link finder in the Hebrew wikipedia. It workd nicely! I have one suggestion: If it finishes and all the links are correct, could you show a green flag, so that we can know that the check is finished and all the links work? Thanks! --Yoavd (Diskussion) 13:58, 29. Jun. 2016 (CEST)Beantworten

Hey Yoavd, first of all thanks for your feedback and it is great to hear that my tool is helpful for you. There is already a feature that informs you when the checks are done and no dead links were found. It is disabled by default. Take a look at the documentation of the OK Icon on how to enable it and for further options. --Frog23 (Diskussion)

I found a strange bug: in this https://he.wikipedia.org/wiki/%D7%94%D7%AA%D7%A7%D7%95%D7%95%D7%94 your tool signaled that there are dead links in the third link [1] which is perfectly working. Also the fifth link is shown as dead [2] and it works. In both cases it shows XX1 Could Not Reach Server, but when I tried manually it was reached instantly. 4 more links (in the remarks) showed the same problem and all of them are working. --Yoavd (Diskussion) 14:39, 29. Jun. 2016 (CEST)Beantworten

Hello again, here is another example: [3] where the dead link finder finds 19 dead links (all of them from the same site, with XX1) but trying manually I get to the site every time. strange. --Yoavd (Diskussion) 10:54, 30. Jun. 2016 (CEST)Beantworten

Thanks for the reports. This might be a DNS issue from the side of the wmflabs-server (the links are checked from there and only the results are reported back to the browser). I tried to check some of the links manually (with curl) after I logged into the server and I couldn't connect to the domains from there as well. as for your last example, I also couldn't retrieve it from my local computer as well. So there is nothing I can do about this now. Maybe this problem is caused by some DNS updates and that the changes haven't fully propagated through yet. This leave the hope that the problem will go again in a day or two. Sorry, I can't be of more help. Bye --Frog23 (Diskussion) 11:34, 30. Jun. 2016 (CEST)Beantworten
Thanks for the answer. In this article [4] I got error 404 but manually I got the link. I seem to understand that some sites are problematic and I will make a list of them. --Yoavd (Diskussion) 11:52, 30. Jun. 2016 (CEST)Beantworten
Hello again, all my findings when you should error 404 proved that the link was indeed dead - so you already helped a lot! Today I got error 400, and the link existed. On the article [5], the fourth remark. --Yoavd (Diskussion) 13:42, 3. Jul. 2016 (CEST)Beantworten