You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Expected behavior
Both buttons should produce an alert window when clicked.
Observed behavior
Only the button labeled "Attribute JS" works in the Log output. Interestingly, the <script> tags are not stripped, and if viewed as HTML, both buttons work as expected.
Desktop (please complete the following information):
OS: Linux
Browser: Firefox
Version: 86.0.1
Additional context
Known to work in earlier versions (independently confirmed in 3.2.1)
The text was updated successfully, but these errors were encountered:
In an effort to focus on bugs and issues that impact currently supported versions of Rundeck, we have elected to notify GitHub issue creators if their issue is classified as stale and close the issue. An issue is identified as stale when there have been no new comments, responses or other activity within the last 12 months. If a closed issue is still present please feel free to open a new Issue against the current version and we will review it. If you are an enterprise customer, please contact your Rundeck Support to assist in your request.
Thank you, The Rundeck Team
Describe the bug
The contents of
<script>
tags in unsanitized HTML are ignored when viewed in the Log Output.My Rundeck detail
To Reproduce
Allow unsanitized HTML output in
framework.properties
Restart Rundeck
Allow unsanitized HTML output on the project
Create a job with a step that outputs the following HTML and add an unsanitized HTML formatter log filter:
Run job with log output as the active tab
Expected behavior
Both buttons should produce an alert window when clicked.
Observed behavior
Only the button labeled "Attribute JS" works in the Log output. Interestingly, the
<script>
tags are not stripped, and if viewed as HTML, both buttons work as expected.Desktop (please complete the following information):
Additional context
Known to work in earlier versions (independently confirmed in 3.2.1)
The text was updated successfully, but these errors were encountered: