Forum Discussion
NimbostratusNeed F5 iRules Consultant - HTTP Header Manipulation Issues
Looking for help with F5 BIG-IP iRules development for custom HTTP header processing. We're trying to modify incoming request headers based on client IP geolocation, but the iRule is causing connection timeouts on certain requests.
The logic works for most traffic but specific user agents seem to trigger infinite loops in the header rewrite code. Need someone experienced with iRules scripting and HTTP event handling to debug the conditional logic.
Seeking 2-3 hours remote troubleshooting to identify and fix the timeout issues. Must be resolved by Thursday for production deployment.
5 Replies
- Injeyan_Kostas
Nacreous
Could you share more info of what you have done so far, what are you trying to achieve and what errors you are facing?
- Paulius
MVP
Can you provide the iRule as well as any irule log errors on the F5 or HTTP status codes or HTTP errors on the client side?
Seattle2kEmployee
Hello Robert,
You may be interested in reaching out to F5 Professional Services. https://www.f5.com/go/contact/request-f5-professional-services
- Melissa_C
Moderator
Hello RobertO09,
I noticed we have there are a few responses from our community requesting some additional information. If you are still looking for community assistance please respond to those, however, if you don't then please update your post and mark as solved.
Thank you for posting to DevCentral!
-Melissa
- Aswin_mk
Need more details to execute it or you can work with with F5 PS. Or These are the most common traps when modifying headers dynamically:
Repeated header modification inside the same event.
If you HTTP::header replace inside an event that triggers again (e.g., because of HTTP::redirect or HTTP::retry), it can loop.Nested or unintended HTTP::collect usage.
Collecting payload multiple times or in the wrong event (like calling HTTP::collect inside HTTP_REQUEST_DATA without checking HTTP::is_collected).
