Forum Discussion
Problem with HTTP::respond, get rid of WWW-Authenticate header
It appears as if the framework has some built in default for 401s
I would agree. The BIG-IP will return a WWW-Authenticate header with a 401 response. Two thoughts off the top of my head:
-
Return a 200 response. It isn't semantically what you're looking for, but technically you're attempting to display HTML content rather than elicit credentials from the user, so it's closer to a 200 than a 401.
-
Drop into layer 4 and scrub the response at the TCP layer. It's a little messier, but it should effectively trick the BIG-IP into not sending the WWW-Authenticate header.
Recent Discussions
Related Content
* Getting Started on DevCentral
* Community Guidelines
* Community Terms of Use / EULA
* Community Ranking Explained
* Community Resources
* Contact the DevCentral Team
* Update MFA on account.f5.com