Skip to content

Document new proxy response codes (452–454/470–477) and X-Massive-Reason header - #64

Open
ilya-yermm wants to merge 1 commit into
mainfrom
docs/PROXY-377-new-response-codes
Open

Document new proxy response codes (452–454/470–477) and X-Massive-Reason header#64
ilya-yermm wants to merge 1 commit into
mainfrom
docs/PROXY-377-new-response-codes

Conversation

@ilya-yermm

@ilya-yermm ilya-yermm commented Aug 14, 2026

Copy link
Copy Markdown
Contributor

No description provided.

@ilya-yermm
ilya-yermm force-pushed the docs/PROXY-377-new-response-codes branch 2 times, most recently from a7319fd to 68a9994 Compare August 14, 2026 14:36
…-Reason

Errors originating inside Massive now use dedicated status codes instead
of generic 5xx, so partners can tell Massive errors from target-site
errors. Rewrites both Error Types pages with the new code table (old ->
new mapping, matching the partner announcement email), documents the
X-Massive-Reason header and SOCKS5 reply bytes, updates usage
restrictions (port block is now 453), sticky-session norotate codes
(502/503 -> 472/475), and the two troubleshooting KB articles.
@ilya-yermm
ilya-yermm force-pushed the docs/PROXY-377-new-response-codes branch from 68a9994 to 0f2a8c3 Compare August 14, 2026 14:38
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant