Forum Discussion
iRule URI rewrites don't always use the correct pool
- Nov 01, 2024
dra1nbama9e Can you please provide the configuration of your virtual server that this is associated to? My guess currently is that that host was sent to the incorrect pool previously and when the new request came in again for the new path it went to the old pool. You can try configuring a /32 OneConnect profile and configuring it on the virtual server in question to see if that corrects the issue.
dra1nbama9e Can you please provide the configuration of your virtual server that this is associated to? My guess currently is that that host was sent to the incorrect pool previously and when the new request came in again for the new path it went to the old pool. You can try configuring a /32 OneConnect profile and configuring it on the virtual server in question to see if that corrects the issue.
- dra1nbama9eNov 04, 2024Altostratus
Hello Paulius
Thank you for the prompt reply. Indeed I configured a /32 oneconnect profile and now is seems that all the requests are redirected only to the correct pool.
Not sure I understand why though :D !- PauliusNov 04, 2024MVP
dra1nbama9e The reason this happens is because the iRule to pool match is only performed on the initial HTTP request from the client. So when the client comes in they match a different part of the iRule and get sent to that pool and then from that point forward every subsequent request is then sent to that same pool. With a OneConnect profile every HTTP request is looked at and a iRule validation of that request is made. The primary use of the OneConnect profile is to reuse connections between the F5 and the pool member but the side-effect is that it looks at every HTTP request and analyzes them separately. The following might help you with some additional understanding.
https://my.f5.com/manage/s/article/K7208
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