We have a significantly sized payload that creates content in Confluence as part of our release documentation. We are seeing these errors consistently while posting content:
"message": "org.codehaus.jackson.JsonParseException: Unexpected end-of-input in VALUE_STRING\n at [Source: com.atlassian.plugins.rest.common.limitrequest.jersey.LimitingRequestFilter$1@2f4690c; line: 1, column: 5249]"
The payload is mighty large to paste in here, but when it's copied verbatim from debug logs into Postman, the same POST message is received, and the server returns with an HTTP 200/OK.
I've inspected the "value" string, and there's no EOL or null characters in there, and it's complete HTML markup. Most of the content is actually coming from a Bitbucket webhook, rendering Pull Request description html.
Is the request volume too high? Is that what a LimitingRequestFilter does?
Please advise,
Thank you
Hi @David Zwarg
Yes, it's what it does:
... ContainerRequestFilter that limits the maximum size of the REST request it will receive.
@Grigory Salnikov Thanks for that link!
Any insight on best practices to creating content on Confluence via the API, if the size of the REST request is limited?
The request that I'm submitting is not very large, ~6K max. Is that hitting the limit of the Confluence REST API?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.