You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
With Jackson 2.12 and earlier inclusion of content snippet for exception messages does not differentiate between textual (json, xml, csv for example) and binary (smile, cbor, for example) content. This leads to attempts to print out control characters for binary content: something that has little value but can be annoying and possibly even unsafe in some cases.
Additionally attempt to print out column/row location are futile as binary formats do not have these concepts.
For 2.13 let's change things so that:
No content snippet is included (at least by default: may consider inclusion of hex values or something later on)
Location information will refer to byte offset (relative to start of content), not row/column
The text was updated successfully, but these errors were encountered:
(note: related to #658, partly #652)
With Jackson 2.12 and earlier inclusion of content snippet for exception messages does not differentiate between textual (json, xml, csv for example) and binary (smile, cbor, for example) content. This leads to attempts to print out control characters for binary content: something that has little value but can be annoying and possibly even unsafe in some cases.
Additionally attempt to print out column/row location are futile as binary formats do not have these concepts.
For 2.13 let's change things so that:
The text was updated successfully, but these errors were encountered: