Github user krishna-pandey commented on the issue:
https://github.com/apache/zeppelin/pull/2492
@Leemoonsoo, @felixcheung, @jongyoul, @prabhjyotsingh Please help review
this.
Note: Chrome Browser seems to be ignoring "X-XSS-Protection" header when
value is set to 1. Ideally, it should be set to "X-XSS-Protection:1;
mode=block". Difference being when later value is set, the browser will prevent
rendering of the page if an attack is detected rather than sanitizing the page
as in previous case.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
