Learn F5 Technologies, Get Answers & Share Community Solutions Join DevCentral

Filter by:
  • Solution
  • Technology
Answers

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

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.

10
Rate this Question
Comments on this Question
Comment made 10-Jun-2014 by OTS02 594
This is a fantastic bit of documentation! Thank you.
0
Comment made 10-Jun-2014 by What Lies Beneath 6587
Thanks!
0

Answers to this Question

placeholder+image
USER ACCEPTED ANSWER & F5 ACCEPTED ANSWER

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

Image Text

5
Comments on this Answer
Comment made 14-Aug-2015 by Patrik Jonsson 3293
Easily one of my favorite posts on devcentral, thank you very much for this one!
0
Comment made 31-Aug-2016 by Missy 0

Thank you soooo much! This is exactly what I needed!

0
placeholder+image
USER ACCEPTED ANSWER & F5 ACCEPTED ANSWER

v6 - June 2014;

--removed

2
placeholder+image
USER ACCEPTED ANSWER & F5 ACCEPTED ANSWER

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.

1
placeholder+image
USER ACCEPTED ANSWER & F5 ACCEPTED ANSWER

Great chart!!

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

0
Comments on this Answer
Comment made 30-Apr-2014 by What Lies Beneath 6587
Note added to diagram, an arrow was too much. Cheers
0
placeholder+image
USER ACCEPTED ANSWER & F5 ACCEPTED ANSWER

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.

0
placeholder+image
USER ACCEPTED ANSWER & F5 ACCEPTED ANSWER

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

0
Comments on this Answer
Comment made 22-Jan-2014 by IheartF5 2357
?
0
Comment made 30-Apr-2014 by What Lies Beneath 6587
Corrected. Cheers
0
placeholder+image
USER ACCEPTED ANSWER & F5 ACCEPTED ANSWER

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

0
Comments on this Answer
Comment made 25-Mar-2014 by IheartF5 2357
As far as iRule events goes yes it would be..CACHE_UPDATE after HTTP_RESPONSE Are you sure it gets fired on the clientside as shown?
0
Comment made 30-Apr-2014 by What Lies Beneath 6587
Corrected. Cheers
0
placeholder+image
USER ACCEPTED ANSWER & F5 ACCEPTED ANSWER

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

0
placeholder+image
USER ACCEPTED ANSWER & F5 ACCEPTED ANSWER

v5a.

--Removed

0
placeholder+image
USER ACCEPTED ANSWER & F5 ACCEPTED ANSWER

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

0
placeholder+image
USER ACCEPTED ANSWER & F5 ACCEPTED ANSWER

Hi Everyone,

Is the diagram uptodate?

0