Forum Discussion
BIG-IP methods to Fix the “421 Misdirected Request” Error
For those of us that are using the BIG-IP as a reverse proxy to front our internal websites to the world, the recent update to Apache has slapped a big "misdirected request" error across our shop windows.
The fix is that apache is looking for the SNI headers (that's different from the HTTP headers I originally was working with). The solution to this, for us anyway, was published ages ago in the thread: Serverside SNI injection iRule | DevCentral
Drop that in your iRule and the world starts working again.
Peace, Love and chocolate biscuits all round.
Serverside SNI injection iRule | DevCentral - solved the "421 Misdirected Request" error when using BIG-IP as a reverse proxy...
(Admin note: adding this explicitly as a comment for Pete_A and marking as Solution - to increase likelihood of finding.)
2 Replies
Thanks for dropping this use-case / solution pairing Pete_A.
Happy to hear that Kai_Wilke's codeshare still has legs.(I'll further drop the link you provided in a comment associated with you and mark as solution - if you disagree for some reason let me know.)
- Pete_A
Altocumulus
Serverside SNI injection iRule | DevCentral - solved the "421 Misdirected Request" error when using BIG-IP as a reverse proxy...
(Admin note: adding this explicitly as a comment for Pete_A and marking as Solution - to increase likelihood of finding.)
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