Allowing to set the content-type header for direct responses
In the Routes options of the load-balancer, setting up a Direct Response route makes that response returned with a content-type header set to "text/plain". That makes the web browser show the HTML code of the page instead of the web page.
Prompting the user with one tiny extra drop-down menu to set the content-type of the direct response they’re setting up would be very helpful, especially when their origin server have issues that they’re trying to compensate for leveraging F5XC.
-
Étienne Labaume
- Dec 14 2023
Related ideas
I have worked around this by inserting a response header of 'Content-Type: text/html' in the route which takes precedence over the default header of text/plain
We've had a customer during the training course, who was asking the exact same thing. Just the option to replace/update the content-type header should be sufficient.
The WAF blocking page (in XC) is already doing this correctly, so copying the behaviour from there might be an option? If possible, this would really improve the usability of the Direct Response option.