wrong server list is returned #50
Comments
|
Thank you for using speedtest-go! speedtest-go also using In my research, the result of In conclusion, we may have no control over this problem 😢. If you have any good idea or solution, please feel free to leave comment. Thank you! |
|
Dear @showwin, do you know what user agent the speedtest-go client is using? maybe speedtest is doing some user-agent based filtering. Doing the curl request to the server list, i ALWAYS receive the same exact list. I tried 20-30 queries and all got the same closest servers. But with speedtest-go, i would say the list would change on every request, alternating between the close (good) list and the one with the remote servers. Is there any way we could at least fail if using a --server command and the chosen server is not on the list? cause otherwise the user can inadvertently be running against a far away server when he's trying to get a "close one" based on the --list results. |
|
@garci66 Sorry for late response 🙏 |
|
dear Ito
I'll take a look. In the case where I was testing, it was quite frequent.
I'll take a look again. I'll try to get some captures
…On Tue, Aug 3, 2021 at 9:29 PM ITO Shogo ***@***.***> wrote:
@garci66 <https://github.com/garci66> Sorry for late response 🙏
I wrote a test code 1a2a5d1
<1a2a5d1>
to verity that the server list change on every request, though such a
situation did not occur. Despite requesting server list 100 times, I got
the same result 🤔. If you could provide some code to reproduce the
change of list on every request, that would be great.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#50 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ACQV3WB5KJXQ7LL5NW5JKDTT3CCXJANCNFSM5AHZXZ6Q>
.
Triage notifications on the go with GitHub Mobile for iOS
<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675>
or Android
<https://play.google.com/store/apps/details?id=com.github.android&utm_campaign=notification-email>
.
|
|
I also have some inconsistencies with the server list. On a system in Las Vegas, Nevada I consistently get servers in Kansas & Oklahoma. I do not see these issues with the Python client. |
|
Yes, they seem to provide different server lists based on the user agent. I see vastly different server lists when running these two commands: |
|
I am having similar issues once again. This is the list returned by "speedtest-go" while plain (The curl with the custom UA above returns another list as well). Both curls return "close" servers, but the "custom" curl returns the best list (a server in my own ISP for example). The list from speedtest-go, all servers are in brazil... (im in argentina) |
|
Hello @showwin, first of all, thank you for your great job ! speedtest-go is a great solution ! I found out, that there is another URL, which returns server list in JSON format which seems to be correct. The URL is: https://www.speedtest.net/api/js/servers?engine=js&limit=10&https_functional=true I'm not good at GO lang, so I would like to ask you @showwin or anybody else to help me with rewriting the code to accept and parse JSON format. Thanks in advance |
When using version 1.1.2, the
--listcommand is not returning the correct server list. On the same host, just doingcurl https://www.speedtest.net/speedtest-servers-static.phpthe list returns the proper servers (those close to me) but if I use the--listcommand, the closest server is 250km away. Which of course impacts the testing results.This is somehow related to #37 which prevents me from running proper tests since I can't override for the servers closest to my location.
The test is using the pre-built binaries for linux x64 on a centos 7.7 machine. I can provide packet captures if needed,
One detail. This can't be always reproduced... which makes it even more confusing.
The text was updated successfully, but these errors were encountered: