iRule Event Order - HTTPS/SSL - Client & Server Side

[What_Lies_Benea]

So, here's the HTTPS/SSL/TLS iRule Event Order - let me know what's wrong.

Updated to v5 (30/04/2014) below: Added HTTP::disable and HTTP::enable command detail, information on persistence and SSL::renegotiate, SSL::profile, SSL::respond and HTTP::respond command detail. Added some events and fixed the WA/AAM stuff.

Updated to v6 - June 2014. Added XML profile and event, other minor corrections.

Updated to v7 September 2014. Reordered some server side events, added further notes.

[IheartF5_45022]

Great chart!!

After CACHE_RESPONSE - it will also go back to HTTP_REQUEST should Keepalive be enabled/supported.

[What_Lies_Bene1]

Note added to diagram, an arrow was too much. Cheers

[What_Lies_Bene1]

Thank you, it's appreciated, it's amazing how little feedback these things get, good or bad.

Regarding CACHE_RESPONSE I would expect the next event to be CLIENT_DATA, as you say, if Keepalive is enabled. I should probably add an arrow (with some text) for that and move CACHE_RESPONSE as it kind of looks like the next event is client closed.

I'll get an update in but it'll have to wait till Monday. Thanks again.

[IheartF5_45022]

Hi you've show WAM request processing but not the response processing after HTTP_RESPONSE - can you add that in please. Jo

[IheartF5_45022]

?

[What_Lies_Bene1]

Corrected. Cheers

[What_Lies_Bene1]

Sorry, not been on here in a while. Would that just be the CACHE_UPDATE event?

[What_Lies_Bene1]

Updated to v4 (29/04/2014) below: Added HTTP::disable and HTTP::enable command detail, information on persistence and SSL::renegotiate, SSL::profile, SSL::respond and HTTP::respond command detail.

[What_Lies_Bene1]

v5. Added some events and fixed the WA/AAM stuff.

[What_Lies_Bene1]

v5a.

--Removed

[What_Lies_Bene1]

v6 - June 2014;

--removed

[OTS02]

This is a fantastic bit of documentation! Thank you.

[What_Lies_Bene1]

Thanks!

[What_Lies_Bene1 · Accepted solution]

Updated to v7 September 2014. Reordered some server side events, added further notes.

*please click to open image and download. Image will expand with correct detail if zoomed in.

[Chase_Abbott]

Hi Jason. This answer was buried in "More Answers" and not easily available. I've marked it as "Selected as best" so now the results are surfaced to the top of the list of replies. Download the image and you can expand it for a great detailed view.

[Algebraic_Mirror]

Anyone know where the ECA events fit with all this? Does ECA processing happen before or after the HTTP_REQUEST type of events?

[Angel_Sosa_Veri]

Hi Everyone,

Is the diagram uptodate?