OK, in case you are able to get through to a technical person there, here is what you could ask:
We would like to know if they are blocking plain http requests with certain user agents, in particular the user agent "LFS".
More information: The game "Live for Speed" makes plain http requests with user agent "LFS" for in-game downloads from the domain "lfs.net" which is a legitimate, low volume use of your internet connection and should be allowed.
EDIT: From my point of view, everyone who has this problem (LFS online working fine but skins, mods, event list, mod browser not working) is welcome to contact their ISP and quote the bold text above or some version of it. Unfortunately I don't have a developer's hotline or anything like that. Their technical people are welcome to contact us if they like.
But fairly sure now it won't make a difference. It didn't really make sense anyway, as people from other UK ISPs can connect fine, not blocked by Cloudflare.
I've now set a rule to skip user agent blocking if user agent is LFS.
But although I looked around for a while, I can't see any evidence that user agent would have been blocked, so I have very low confidence that this will change anything.
Anyway, at least it didn't break anything for me. Let's see if this helps our BT users.
EDIT:
Attached image, showing some options. I've selected to skip "User Agent Blocking" but I don't think we have any user agent blocking enabled so skipping it probably won't affect anything. Maybe if the current change doesn't help at all I can try another option, e.g. "Browser Integrity Check" in case that might do something.
Still, I don't see why Cloudflare would only apply blocking rules to BT customers.
It's more because I am just a game programmer. I'm not the overlord of the internet.
I'm just one guy sitting in a house trying to make a nice game. There's no way that I can be expected to increase the stability of the global internet in the face of ever increasing usage, attacks and political instability. Maybe the best times of the internet are now in the past, for a while.
I thought as much too but seeing as the UK issues are 100% BT customers, and the rest of us also go through Cloudflare, it seems to point at BT more than Cloudflare.
First of all you are confusing two completely separate issues.
Issue 1) British users at BT who have absolutely no problem at all with any of LFS services apart from one very specific type of traffic: http requests from LFS.exe to our web server, downloading images, mods or mod list.
NOTE: These users have no other issue between their computer and our servers. This currently points to BT traffic shaping as the only thing I can think of. Once again, I cannot and will not stop developing the new full version, at this time, to deal with BT traffic shaping or whatever it is that doesn't affect anyone in Europe other than BT users in the UK.
Issue 2) You are having problems with all types of connection to LFS servers, from Singapore to the Netherlands. There is no way that this can be explained by a problem with the i3d internet connection that is working fine for most people. It's a long way between Singapore and the Netherlands and we cannot be held responsible for the behaviour of multiple internet routers around the world.
REPEAT: You are talking about a separate, unrelated issue.
I am serious busy working 12 to 14 hour days trying to finish the new version - and nothing has changed in LFS code pages in recent times.
So, please. before I look into it at all can you have a look to see DIRECTLY the output from LFS? Special Japanese characters are output as double-byte characters from Windows code page 932
LFS.exe has absolutely no knowledge or implementation of anything to do with UTF-8 etc.
It only knows single byte ASCII and code pages (including double-byte code pages for Chinese Japanese and Korean). It does not do UTF-8 or any kind of UTF.
This forum section is purely to let me know about LFS bugs, for me to fix. But people are reporting issues with text strings that other programs have already converted.
It has also been proved that if you use a different internet connection, the problem goes away.
So the problem, for the UK users, appears to be BT. The only possibility I can think of is that they are restricting http traffic from sources they don't understand. LFS connects with a "user agent" called "LFS" rather than "Firefox" etc. So maybe BT suspects it is a bot or web crawler. This is speculation.
Seeing as it's pretty much only BT users that have this issue, the ideal people to fix the issue would be BT, if they would kindly avoid traffic shaping that would be appreciated.
Alternatively we can try experimenting, so that LFS 'spoofs' its user agent to try to appear like Firefox. But I am seriously much too busy, currently working on average 12 hour days to try and get this release finished, so I can't start messing around now trying to get around BT's traffic shaping.
Basically I would like to know if:
1) replays saved after you restart your host, now have the correct date?
or:
2) You restarted your host but new replays recorded after the restart, still say 20 July?
My test: I started a host and recorded a replay. Restarted the host on a different server and saved another replay. Both have the correct date.
Restarting the host will not correct the replays that were already recorded in the past, but hopefully new replays have the correct date.
OK, I can't really understand how this has happened.
It seems like something might have happened on that server at that point in time, probably affecting all hosts running on that server, so the function "GetSystemTimeAsFileTime" always returned the same value, and that value was implanted into the replays.
It seems that it will be fixed if you restart your host, and that's what I suggest at this point.
I am trying to investigate the cause of a strange issue for some users, particularly some of our UK users with BT internet. They have connections that appear to work well, and our website works as expected, but downloads in game run very slowly (skins, mods, mods browser, event list). We are talking VERY slowly: 15 seconds for a small image, 10 minutes for a mod.
If you do have that problem, please visit the special thread on that subject. There are some tests you can try if you set your browser to allow http connections (LFS uses http connections, not https, but this does not seem to be directly the cause of the issue).