STREAM::expression and "thread safety"

For the HTTP profile, HTTP pipelining is enabled by default, but current browsers do not enable pipelining by default.

 

If pipelining is enabled on the HTTP profile, as per

 

AskF5 Home > Knowledge Center > BIG-IP LTM > BIG-IP Local Traffic Management: Profiles Reference > Services Profiles

 

Support for pipelining

 

Normally, a client cannot initiate a request until the previous request has received a response. HTTP/1.1 pipelining allows clients to initiate multiple requests even when prior requests have not received a response. Note, however, that each initiated request is still processed sequentially; that is, a request in the queue is not processed until the previous request has received a response.

 

By enabling support for pipelining on the BIG-IP® system, you remove the need to enable pipelining on the destination server itself. By default, this feature is enabled.

 

So you will always get a sequential HTTP_REQUEST/HTTP_RESPONSE for an HTTP profile, and there should be no concerns about event ordering.

 

I'll provide a separate answer for the HTTP/2 profile when I get some more information.