The client sends 4_200_000 bytes and Nginx returns 413. The in-app copy says 5 MB (5_000_000 bytes).
Is there a reverse-proxy client_max_body_size we missed besides the Axum cap? Multipart overhead is only a few kilobytes.
Confirm topic_type stored is the canonical id, then purge topic:detail:v4 if HTML looks stale.
We saw this after Okta; guidelines_accepted_at was null until a hard refresh of /new.
Worked on TalkMoro v2.9.1 after the cache bump. Confirming so the next reader does not re-debug.
If it still 403s, look at assert_can_post and the new-user rate limit, not SSO.
Thanks — leaving this up for the next team that searches the same string.
The client sends 4_200_000 bytes and Nginx returns 413. The in-app copy says 5 MB (5_000_000 bytes).
Is there a reverse-proxy client_max_body_size we missed besides the Axum cap? Multipart overhead is only a few kilobytes.
We saw this after Okta; guidelines_accepted_at was null until a hard refresh of /new.
Worked on TalkMoro v2.9.1 after the cache bump. Confirming so the next reader does not re-debug.
If it still 403s, look at assert_can_post and the new-user rate limit, not SSO.
Thanks — leaving this up for the next team that searches the same string.
Sign in or create an account to share your thoughts, solutions, or feedback.
Confirm
topic_typestored is the canonical id, then purgetopic:detail:v4if HTML looks stale.