Loading...
Loading...
If JavaScript code contains multi-byte character which contains 0x0A in the last byte after conversion to UTF-32 form, then this character is handled as NEW LINE by Portal Access server-side JavaScript parser. If NEW LINE is not valid in this place, JavaScript code cannot be parsed.
Web application may not work correctly.
JavaScript code with multi-byte character which contains 0x0A in the last byte after conversion to UTF-32 form, for example: //? aa bb (?) gives (4E 0A) in UTF32 form. So this line is processed as the following TWO lines: // aa bb The second line is not a valid JavaScript code.
There is no workaround at this time.
Now Portal Access JavaScript parser handles multi-byte characters correctly.
Click on a version to see all relevant bugs
F5 Integration
Learn more about where this data comes from
Bug Scrub Advisor
Streamline upgrades with automated vendor bug scrubs
BugZero Enterprise
Wish you caught this bug sooner? Get proactive today.