I'd like to extend this request to not only support the content-type "application/json", but any other MIME type as well. As XC does send responses (not only in WAF, but for direct response routes or rate limiter as well) only as Content-Type "text/plain", the browser will never render HTML as HTML, because we tell our browsers since ages, to not sniff the mime-type ;-)

This missing feature leads to more and more customer complaints.

The F5XC WAF blocking page should support the JSON content type, similar to AWAF AJAX, to enhance compatibility with modern applications that rely on structured JSON responses for error handling. This ensures consistency with AWAF, facilitates better integration with clients that process blocking events programmatically, and improves user experience by allowing applications to handle restrictions more effectively.