Forum Discussion
Julie
Altostratus
I've made sure that the JSON profile is is first in line, but looking more closely at this, I'm seeing that the problematic POST requests are coming in as
Content-Type: text/plain
with
Accept: application/json, text/javascript, */*; q=0.01
I'm assuming this explains why it's not parsing properly? Or should it be recognizing the content as JSON automatically?
Ivan_Chernenkii
Aug 24, 2020Employee
Hello Julie,
Could you provide example of failed requests and configuration of "Header-Based Content Profiles" of URL in policy, which this request matches?
Thanks, Ivan