iRules Insight - HTTP Event Order
I'm a visual learner. You know this about me. I've said as much in earlier posts (Me Caveman, Need Picture). So it should come as no surprise that I'll be highlighting a picture here. A picture is worth a thous...yada yada yada, you get it. I see many drawings, all of which are purposed to convey some type of information. This, however, is a visual treasure chest building on the event ordering goodness discussed by Colin a while back that hones in on the flow of data through the iRules events specific to the HTTP protocol. If you develop iRules for HTTP traffic, you need this diagram in your toolbox. Major thanks to F5er John Alam for putting this gem together!
Update: Click Here for the lastest drawing, which was refreshed 02/01/2011.
AdminAdmin- JRahm@James .. Wow, that's great! Thanks for sharing. I'll need to dig into that for a while, that's an immense amount of data in there.
- JRahm@linjin - you can buffer all the payload in a request with HTTP::collect. If you don't need it all, you can specify the length as an option. The wiki page for HTTP::collect is devcentral.f5.com/.../HTTP__collect.html
- JRahm@linjing, you're correct there is no content-length in the request, I think the object was copied and that specific text was not trimmed from the diagram.
