https Monitor receive string / regexp ^(caret)

Hi Rolf,

 

 

I don't think this is the issue, but the receive string you have listed would probably fail if the server responds with a 304 as a 304 wouldn't have OK after the status code. It should be Not Modified or something similar. You might try:

 

 

HTTP/(1.0|1.1) (200 OK|304 Not Modified)

 

 

If it works with HTTP but not HTTPS, you could try capturing a tcpdump and make sure that the first character in the decrypted HTTP is HTTP. I expect it would be, but it would be good to double check. It sounds like this might be a bug. The monitor receive string should be applied to the decrypted response content, so theoretically, that anchor tag in the regex receive string should work for HTTPS the same as it does for HTTP.

 

 

If you don't get a definitive answer here, you might try opening a case with F5 Support.

 

 

Aaron