If you're encountering 400s when using special characters and the Cortex API, it's likely due to a security-related block for our web framework.
Cortex Self-Managed/Hosted:
Add the following variables into your backend secrets/configmap and restart:
JAVA_OPTS: "-Dorg.apache.tomcat.util.buf.UDecoder.ALLOW_ENCODED_SLASH=true"
JAVA_TOOL_OPTS: "-Dorg.apache.tomcat.util.buf.UDecoder.ALLOW_ENCODED_SLASH=true"
Cortex Cloud/SaaS:
This is a known limitation. Changing the entity tag to remove/replace the special character will result in a successful API call.
Comments
0 comments
Article is closed for comments.