problem with X

[pourya-p]

the time line does not load and response with 422 or 404 status code

the explorer reqs:

POST /i/api/graphql/jYMvLJJjGjO3aKWY3bP5HA/HomeTimeline HTTP/1.1
Accept: /
Accept-Encoding: gzip, deflate, br, zstd
Accept-Language: en-US,en;q=0.9
Connection: keep-alive
Content-Length: 2316
Cookie: ***
Host: www.x.com
Origin: https://www.x.com
Referer: https://www.x.com/home
Sec-Fetch-Dest: empty
Sec-Fetch-Mode: cors
Sec-Fetch-Site: same-origin
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/145.0.0.0 Safari/537.36 Edg/145.0.0.0
authorization: Bearer ***
content-type: application/json
sec-ch-ua: "Not:A-Brand";v="99", "Microsoft Edge";v="145", "Chromium";v="145"
sec-ch-ua-mobile: ?0
sec-ch-ua-platform: "Windows"
x-csrf-token: 4514e6cb191d21ed5945c27e401fd3f341291dc2602e3c14d110b60d9fdfcc223c2c101d2d427fb707f334dedf560a644c4130fae2f0f3276e0898bc7bb6e
x-twitter-active-user: yes
x-twitter-auth-type: OAuth2Session
x-twitter-client-language: en

HTTP/1.1 422 OK
Access-Control-Allow-Origin: https://www.x.com
Access-Control-Expose-Headers: X-Acted-As-User-Id,X-Rate-Limit-Limit,X-Rate-Limit-Remaining,X-Rate-Limit-Reset,X-TD-Mtime
Cache-Control: no-cache, no-store, max-age=0
Content-Type: application/json
Date: Mon, 04 May 2026 06:43:20 GMT
Server: cloudflare envoy
Set-Cookie: ***
Strict-Transport-Security: max-age=631138519; includeSubdomains
Vary: accept-encoding
cf-cache-status: DYNAMIC
cf-ray: 9f6587d46bcfed7f-ATL
origin-cf-ray: 9f6587d46bcfed7f-ATL
perf: 7402827104
x-rate-limit-limit: 500
x-rate-limit-remaining: 490
x-rate-limit-reset: 1777877699
x-response-time: 21
x-served-by: t4_a
x-trace-id: 0000000000000000d17963422176fcc8
x-transaction-id: d17963422176fcc8
Content-Length: 172

POST /i/api/1.1/graphql/user_flow.json HTTP/1.1
Accept: /
Accept-Encoding: gzip, deflate, br, zstd
Accept-Language: en-US,en;q=0.9
Connection: keep-alive
Content-Length: 5593
Cookie: ***
Host: www.x.com
Origin: https://www.x.com
Referer: https://www.x.com/home
Sec-Fetch-Dest: empty
Sec-Fetch-Mode: cors
Sec-Fetch-Site: same-origin
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/145.0.0.0 Safari/537.36 Edg/145.0.0.0
authorization: Bearer ***
content-type: application/x-www-form-urlencoded
sec-ch-ua: "Not:A-Brand";v="99", "Microsoft Edge";v="145", "Chromium";v="145"
sec-ch-ua-mobile: ?0
sec-ch-ua-platform: "Windows"
x-csrf-token: 4514e6cb191d21ed5945c27e401fd3f341291dc2602e3c14d110b60d9fdfcc223c2c101d2d427fb707f334dedf560a644c4130fae2f0f3276e0898bc7bb6e
x-twitter-active-user: yes
x-twitter-auth-type: OAuth2Session
x-twitter-client-language: en

HTTP/1.1 404 Not Found
Access-Control-Allow-Origin: https://www.x.com
Access-Control-Expose-Headers: X-Acted-As-User-Id,X-Rate-Limit-Limit,X-Rate-Limit-Remaining,X-Rate-Limit-Reset,X-TD-Mtime
Cache-Control: no-cache, no-store, max-age=0
Date: Mon, 04 May 2026 06:43:20 GMT
Server: cloudflare envoy
Set-Cookie: ***
Strict-Transport-Security: max-age=631138519; includeSubdomains
cf-cache-status: DYNAMIC
cf-ray: 9f6587d79b94b16c-ATL
origin-cf-ray: 9f6587d79b94b16c-ATL
perf: 7402827104
x-response-time: 2
x-served-by: t4_a
x-transaction-id: a32e4c29cc6c90bf
Content-Length: 0

POST /i/api/1.1/graphql/error_log.json HTTP/1.1
Accept: /
Accept-Encoding: gzip, deflate, br, zstd
Accept-Language: en-US,en;q=0.9
Connection: keep-alive
Content-Length: 2376
Cookie: ***
Host: www.x.com
Origin: https://www.x.com
Referer: https://www.x.com/home
Sec-Fetch-Dest: empty
Sec-Fetch-Mode: cors
Sec-Fetch-Site: same-origin
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/145.0.0.0 Safari/537.36 Edg/145.0.0.0
authorization: Bearer ***
content-type: application/x-www-form-urlencoded
sec-ch-ua: "Not:A-Brand";v="99", "Microsoft Edge";v="145", "Chromium";v="145"
sec-ch-ua-mobile: ?0
sec-ch-ua-platform: "Windows"
x-csrf-token: 4514e6cb191d21ed5945c27e401fd3f341291dc2602e3c14d110b60d9fdfcc223c2c101d2d427fb707f334dedf560a644c4130fae2f0f3276e0898bc7bb6e
x-twitter-active-user: yes
x-twitter-auth-type: OAuth2Session
x-twitter-client-language: en

HTTP/1.1 404 Not Found
Access-Control-Allow-Origin: https://www.x.com
Access-Control-Expose-Headers: X-Acted-As-User-Id,X-Rate-Limit-Limit,X-Rate-Limit-Remaining,X-Rate-Limit-Reset,X-TD-Mtime
Cache-Control: no-cache, no-store, max-age=0
Date: Mon, 04 May 2026 06:43:21 GMT
Server: cloudflare envoy
Set-Cookie: ***
Strict-Transport-Security: max-age=631138519; includeSubdomains
cf-cache-status: DYNAMIC
cf-ray: 9f6587dcaeb4055a-ATL
origin-cf-ray: 9f6587dcaeb4055a-ATL
perf: 7402827104
x-response-time: 3
x-served-by: t4_a
x-transaction-id: 3715994650c4cbdf
Content-Length: 0

##your app log:
2026-05-04T06:44:47.948117Z INFO relay POST https://www.x.com/i/api/graphql/jYMvLJJjGjO3aKWY3bP5HA/HomeTimeline
2026-05-04T06:44:48.491920Z INFO relay POST https://www.x.com/i/api/1.1/graphql/user_flow.json
2026-05-04T06:44:49.573564Z INFO relay POST https://www.x.com/i/api/1.1/graphql/error_log.json
2026-05-04T06:44:52.572037Z INFO relay POST https://www.x.com/i/api/1.1/graphql/user_flow.json

##the config:
{
"mode": "apps_script",
"google_ip": "216.239.38.120",
"front_domain": "www.google.com",
"script_id": "",
"auth_key": "",
"listen_host": "127.0.0.1",
"listen_port": 8085,
"socks5_port": 8086,
"log_level": "debug",
"verify_ssl": true,
"sni_hosts": [
"www.google.com",
"mail.google.com",
"accounts.google.com"
],
"normalize_x_graphql": true,
"max_ips_to_scan": 100,
"scan_batch_size": 500,
"google_ip_validation": true,
"tunnel_doh": true
}

Originally posted by @pourya-p in #64

[therealaleph]

@(author) — X's GraphQL endpoints often return 422 / 404 when the features / fieldToggles query parameters change between client and server expectations. v1.9.0+ has a config knob for exactly this:

"normalize_x_graphql": true

When set, GET requests to x.com/i/api/graphql/<hash>/<op>?variables=… have the features and fieldToggles params stripped before being relayed. X's response cache hit rate goes up dramatically + 422s caused by feature-flag drift go away.

Off by default because some endpoints actually require features (rare — observe and adjust). Try with the flag on and report back if you still see 422 / 404.

For POST endpoints (mutations like Like / RT / Reply), this knob doesn't help — those have their own anti-automation gating. CF anti-bot also affects X — set up an exit-node (assets/exit_node/README.md) and add x.com to exit_node.hosts if you're getting 4xx after rate-limit retries.

---

_{[reply via Anthropic Claude | reviewed by @therealaleph]}