Loading...
Loading...
Enabling any JavaScript injection interferes with <meta http-equiv="X-UA-Compatible" content="..."> when it is included in the HTML response from the back-end server.
The impact is that pages loaded in Internet Explorer may be loaded in compatibility mode instead of following the X-UA-Compatible header.
-- The back-end web server uses <meta http-equiv="X-UA-Compatible" content="..."> header in the HTML and relies on it for displaying Internet Explorer content. -- Users using Internet Explorer to access the Virtual Server -- JavaScript injection is enabled from any of the ASM features, such as: DoS Profile: Single Page Application Bot Defense Profile: Single Page Application, Verify After Access, Generate After Access ASM Policy: CSRF, AJAX Blocking Page, Web Scraping - Bot Detection
For injections coming from DoS or Bot Defense: Modify the DB variable which controls the location of the injection: -- tmsh modify sys db dosl7.parse_html_inject_tags value before,script,before,/head,before,body This will cause the script to be injected after the first <script> tag, or before the </head> tag, which ever comes first on the response HTML. For injections coming from the ASM Policy: -- /usr/share/ts/bin/add_del_internal add smart_inject 1 -- bigstart restart asm This will cause the JavaScript to be injected after the X-UA-Compatible header, if such header exists on the response HTML.
None
Click on a version to see all relevant bugs
F5 Integration
Learn more about where this data comes from
BugZero Plan
Streamline upgrades with automated vendor bug scrubs
BugZero Prevent
Wish you caught this bug sooner? Get proactive today.