Tarkov got really popular this week but is down a lot this weekend because the servers are getting hammered. Even inventory transactions go through the server for each one. When these fail, you get an error box with a big XML message. So I am just sayin' ...
-
-
That looks like a canned error response from an L7 load balancer/request router. I wouldn’t assume the game client and server are using the same protocol.
-
These happen as a result of routine game actions like moving an item in your inventory.
- Još 2 druga odgovora
Novi razgovor -
-
-
Can I recommend actually having a look at the raw traffic between you and the game servers rather than jumping to conclusions on how it’s implemented? Because this error being HTML doesn’t actually suggest anything about how it’s implemented at all
-
It looks like HTTPS on prod. is just their login server (which makes sense because you can register and login through their website too)
- Još 2 druga odgovora
Novi razgovor -
-
-
Playing devil's advocate, this could work as long as their backend was designed to auto-scale. It will cost quite a bit in operation, but could have been avoided with enough money (to hire cloud devs & rent VMs). Usually not afforded to small studios. We really need better OSS.
-
Except .. it's not. A ton of people bought the game, so they have money to scale it up, and .. perf still sucks.
- Još 1 odgovor
Novi razgovor -
-
-
The game needs to know if the bullets went into <head> or <body>
Hvala. Twitter će to iskoristiti za poboljšanje vaše vremenske crte. PoništiPoništi
-
-
-
Googling part of that html seems to point to cloudflare.
-
Maybe they're using a REST API, using Cloudflare as a load balancer, which is treating it like a web request, hence the HTTP response format? - Još 1 odgovor
Novi razgovor -
-
-
It looks like an error from a load balancer.
Hvala. Twitter će to iskoristiti za poboljšanje vaše vremenske crte. PoništiPoništi
-
Čini se da učitavanje traje već neko vrijeme.
Twitter je možda preopterećen ili ima kratkotrajnih poteškoća u radu. Pokušajte ponovno ili potražite dodatne informacije u odjeljku Status Twittera.