Lemmy

12535 readers

2 users here now

Everything about Lemmy; bugs, gripes, praises, and advocacy.

For discussion about the lemmy.ml instance, go to !meta@lemmy.ml.

founded 4 years ago

MODERATORS

nutomic@lemmy.ml

When does commenting return "invalid_body_field" in the API? (lemmy.world)

submitted 1 year ago by AlmightySnoo@lemmy.world to c/lemmy@lemmy.ml

4 comments fedilink hide all child comments

I'm inclined to say it happens to comments that are too long but I'm not sure it's the only case where it happens. It seems the API simply returns a 400 error with "invalid_body_field" as the response. The web UI however just displays an infinite spinning wheel with no helpful error message.

you are viewing a single comment's thread
view the rest of the comments

[–] WalterLatrans@yiffit.net 2 points 1 year ago* (last edited 1 year ago) (1 children)

I had a peek at the source code and although I don't actually know Rust it looks like that error comes from a check for character length in the function "is_valid_body_field". Strangely it does the same check twice against two variables "POST_BODY_MAX_LENGTH" and "BODY_MAX_LENGTH".

The smaller of the two is BODY_MAX_LENGTH which is set at 10000, so I assume the max character limit is 10,000. There are no other checks in that function other than the character count and that's the only place in the source code that the text "invalid_body_field" shows up so I assume it's only sent as a response to too much text, but as I said I don't actually know Rust so I could be wrong.

[–] AlmightySnoo@lemmy.world 2 points 1 year ago* (last edited 1 year ago)

I just checked validation.rs (line 132) too and you're right!