Unrealistic upload speeds using Safari

[openspeedtest]

Unrealistic upload speeds using Safari

[Steffen75]

I found the problem. Safari's console was reporting HTTP errors 405 during the upload due to the static design of OST.

So I added error_page 405 =200 $uri; to the config and now it works.

But what about adding a server side php script for making a real upload to /dev/null as an improvement in a future version. Using PUT should make it rather simple.

[openspeedtest]

Delete browser cache or try in private window. Did you used previous version on the same IP address / ports?One of my friend reported an issue like this but after deleting cache/running from private window solved the issue. If the problem still exists, take a look at Safari browser console. Must be server configuration error. Did you try OpenSpeedTest-Server or docker image? And able to reproduce this issue? Can you Post your Nginx config. You must follow https://github.com/openspeedtest/Nginx-Configuration

[openspeedtest]

Nginx will read the post body and pass it to static file. It will get discarded like dev/null.

Yes we can use PHP or any other languages to do the same stuff.

But static design means you don't have to worry about security updates for your programming language.

More secure, easy to deploy, run anywhere all you need is basic web server.

That is why I am able to create Android and iOS apps with the same files that is posted here.

If it does what we need means why should we need a programming language like PHP anyway.

[arekm]

Why 405 response POST entries are taken into account anyway? These are errors and maybe should be shown to user instead of being counted for upload speed.

(that's from Speed-Test deployed on pfSense http management server)

[openspeedtest]

@arekm Some browsers, like Safari, may not trigger the onProgress event if the request completes in under 100 milliseconds. This is a known issue with Safari and Internet Explorer (IE). Therefore, when testing very fast connections, we might not receive the onProgress event, prompting us to calculate it manually using onLoad event. This behavior is only likely to occur if the server is not configured correctly and is generally not encountered in standard use.

[arekm]

I'm using google chrome 122 (and the server isn't configured for speedtest purposes, that's for sure).

[openspeedtest]

@arekm Which Server? If that is Nginx check https://github.com/openspeedtest/Nginx-Configuration/blob/main/OpenSpeedTest-Server.conf#L29 If that is not Nginx, Handle /upload and return 200.

[arekm]

Configuration of that server cannot be changed (it's autogenerated nginx config from pfSense software for purposes of pfSense panel management only and speed test is only sneaked into it to be able to test speeds to/from pfSense router).

I'm only mentioning that problem to see if there is a way to better handle 405 error in such "not correctly configured server c" case, instead of showing up crazy results.

[openspeedtest]

@arekm Even when the server is configured correctly, Safari at very high speed may not fire the OnProgress event. Otherwise, we would need to drop support for Safari, which is not an option. Unfortunately, I am not aware of a better way to avoid this issue.

[openspeedtest]

@arekm Maybe we can stop the upload process and warn the user if the server returns a 405 (Method Not Allowed) status code.

if (xhr.status === 405) {
    // Handle the 405 error
    console.error("Error: Method Not Allowed (405)");

I will test this, and if possible, I will update the speed test soon.