Loading...
Loading...
When a string field in the JSON schema has minLength/maxLength constraints, they are incorrectly interpreted as constraints on the number of bytes instead of the number of characters.
Requests incorrectly blocked, due to interpreting the constraints as byte length rather than character length.
JSON profile with a schema that includes a string field with minLength and maxLength constraints.
NoneString fields in JSON schema now correctly interpret minLength/maxLength constraints based on character length rather than byte length
String fields in JSON schema now correctly interpret minLength/maxLength constraints based on character length rather than byte length
F5 Integration
Learn more about where this data comes from
BugZero Plan
Streamline upgrades with automated vendor bug scrubs
BugZero Prevent
Wish you caught this bug sooner? Get proactive today.