The issue I am facing is that on AJAX pages, the HTML is not executed. We can get to the blocking response page by either specifying a response type of "Redirect URL" or specifying a custom response header (see below):
HTTP/1.1 301 Moved Permanently
The problem is that in either of these cases, the support ID does not appear. Any further ideas?
(BTW, the custom response HTML is exactly like that in 7825, that is:
To be clear, the support ID variable is being substituted in the response HTML. It is NOT being substituted in the custom response header. I also thought that if we specified a type of "Redirect URL" instead of "Csutom Response", that the support ID variable would be substituted in the URL.
I guess not... So is this expected behavior or a bug?
That makes more sense. The ability to insert the support ID in redirects was "lost" around 9.4.x. You can workaround this limitation by using the custom response with a meta-refresh. I'm fairly sure there is a CR requesting the addition of this back. You could open a case with F5 Support asking to have your case attached to the CR to raise its visibility.