-
-
Notifications
You must be signed in to change notification settings - Fork 791
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add configurable limit for the maximum number of bytes/chars of content to parse before failing #1046
Labels
2.16
Issue planned (at earliest) for 2.16
processing-limits
Issues related to limiting aspects of input/output that can be processed without exception
Comments
cowtowncoder
added
2.16
Issue planned (at earliest) for 2.16
processing-limits
Issues related to limiting aspects of input/output that can be processed without exception
labels
Jun 12, 2023
I guess built-in support would be good - but this limit is straightforward for users to apply themselves without waiting for a jackson solution. If your input data is the form of
|
Still hoping to get this in 2.16 as it would be the last processing limit formally requested. But we'll see :) |
cowtowncoder
added a commit
that referenced
this issue
Sep 6, 2023
cowtowncoder
added a commit
that referenced
this issue
Sep 8, 2023
Implemented for JSON backend ( |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
2.16
Issue planned (at earliest) for 2.16
processing-limits
Issues related to limiting aspects of input/output that can be processed without exception
(note: part of #637)
Jackson 2.15 included a few processing limits that can be applied to limit processing for "too big content"; first focusing on general nesting depth and max. length of individual tokens.
While this is good first step, it also makes sense to offer a simple way to limit maximum content in total allowed to be read -- typically a maximum document size, but in case of line-delimited input, maximum streaming content.
The reasoning for addition of such feature is that although users can -- if they must -- implement this at yet lower level (length-limited
InputStream
, for example), there are some benefits from Jackson streaming component offering this:StreamConstraintsException
)Note, too, that this feature significantly improves usefulness (or right now, lack thereof) of #863 to combine per-token limits with overall limits.
NOTE: the default setting for this limits should, however, be left as "unlimited": using anything else is likely to break some processing somewhere.
Limit has to be defined as 64-bit
long
(notint
); default value to use then is likelyLong.MAX_VALUE
.The text was updated successfully, but these errors were encountered: