New request limits? (429 error)

[JVz]

there is always risk of getting banned with steam

[Nickers]

On 7/12/2026 at 8:38 PM, vindisel said:

'Accept-Encoding': 'br, zstd'

This still seems to work fine for me atm. But Steam seems to go through a bit of turbulence right now, so I catch stray 500's and 400's

 

3 hours ago, rahimi0151 said:

I have asked gpt5.5 to fix it.

I'm afraid it's specific Steam-related problem from recent site changes and GPT won't have that in it's training data.
Did it give any guesses on why this might work?

 

2 hours ago, JVz said:

There is always risk of getting banned with steam

Many years of being afraid for my normal trading accounts T ^ T

[4049_1572836826]

Something big comming 🤫 - steam has new cookies bm_sv and ak_bmsc

Quote

Used by Akamai Botman Manager to distinguish between human-generated web requests and automated ones, such as those from bots. Used to store information about the web server that is serving the website.

 

Edited July 13 by 4049_1572836826

[skr1pt]

9 hours ago, 4049_1572836826 said:

Something big comming 🤫 - steam has new cookies bm_sv and ak_bmsc

 

steam using this cookies few years) dont panic

[4049_1572836826]

9 hours ago, skr1pt said:

steam using this cookies few years) dont panic

😵‍💫 I was panicking 😅 but thanks for the clarification. This cookie new for me. I've never seen it in cookies since yesterday.

[rahimi0151]

On 7/13/2026 at 9:55 PM, Nickers said:

I'm afraid it's specific Steam-related problem from recent site changes and GPT won't have that in it's training data.
Did it give any guesses on why this might work?

it just brute forced it. I just used "/Goal" mode in codex. it changed a bit, sent a new request, changed a bit, sent a new request, on and on an on, in a loop. for like 30 minutes. 

[vindisel]

On 7/13/2026 at 5:14 PM, vindisel said:

This option also turned out to be quite working, for me it does not even require changing the Accept-Encoding, the key is to transfer Accept and sec-fetch-user.
 

headers: {
    //"User-Agent": "Mozilla/5.0 (Linux; Android 14; Pixel 8) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/140.0.0.0 Mobile Safari/537.36",
    "Accept": "text/html,application/xhtml+xml,application/xml;q=0.9,image/avif,image/webp,image/apng,*/*;q=0.8",
    //"Accept-Encoding": "gzip, deflate, br, zstd",
    "Accept-Language": "en-US,en;q=0.9",
     "sec-ch-ua": "\"Chromium\";v=\"140\", \"Not=A?Brand\";v=\"24\", \"Google Chrome\";v=\"140\"",
    "sec-ch-ua-mobile": "?1",
     "sec-ch-ua-platform": "\"Android\"",
    "sec-fetch-dest": "document",
    "sec-fetch-mode": "navigate",
    "sec-fetch-site": "same-origin",
    "sec-fetch-user": "?1",
    "upgrade-insecure-requests": "1"
}

This fix has been working for 40 hours, there have been no problems with anything. Share who has what results

[Nickers]

On 7/13/2026 at 3:14 PM, vindisel said:

headers: { //"User-Agent": "Mozilla/5.0 (Linux; Android 14; Pixel 😎 AppleWebKit/537.36 (KHTML, like Gecko) Chrome/140.0.0.0 Mobile Safari/537.36", "Accept": "text/html,application/xhtml+xml,application/xml;q=0.9,image/avif,image/webp,image/apng,*/*;q=0.8", //"Accept-Encoding": "gzip, deflate, br, zstd", "Accept-Language": "en-US,en;q=0.9", "sec-ch-ua": "\"Chromium\";v=\"140\", \"Not=A?Brand\";v=\"24\", \"Google Chrome\";v=\"140\"", "sec-ch-ua-mobile": "?1", "sec-ch-ua-platform": "\"Android\"", "sec-fetch-dest": "document", "sec-fetch-mode": "navigate", "sec-fetch-site": "same-origin", "sec-fetch-user": "?1", "upgrade-insecure-requests": "1" }

I only recently switched to this option and not a single error in few days. Previous iteration also worked well with confirmations, but had some issues with inventory loading.

Did last community update fixed this issue? (github people say no)

Edited July 19 by Nickers