Skip to content

Correcting X-XSS-Protection Header #136

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 5 commits into from
May 8, 2019
Merged

Correcting X-XSS-Protection Header #136

merged 5 commits into from
May 8, 2019

Conversation

OhHeyAlan
Copy link
Contributor

X-XSS-Protection sets the configuration for the cross-site scripting filters built into most browsers. The best configuration is "X-XSS-Protection: 1; mode=block".

Was "0"
Now "1; mode=block"

X-XSS-Protection sets the configuration for the cross-site scripting filters built into most browsers. The best configuration is "X-XSS-Protection: 1; mode=block".

Was "0"
Now "1; mode=block"
@jc21
Copy link
Member

jc21 commented May 6, 2019

Docker Image for build 1 is available on DockerHub as jc21/nginx-proxy-manager:github-pr-136-amd64

@jc21
Copy link
Member

jc21 commented May 7, 2019

Can you please re-open this PR against the develop branch?

@OhHeyAlan OhHeyAlan changed the base branch from master to develop May 7, 2019 23:55
@OhHeyAlan
Copy link
Contributor Author

@jc21 Done

@jc21
Copy link
Member

jc21 commented May 7, 2019

Docker Image for build 2 is available on DockerHub as jc21/nginx-proxy-manager:github-pr-136-amd64

@jc21
Copy link
Member

jc21 commented May 8, 2019

Docker Image for build 3 is available on DockerHub as jc21/nginx-proxy-manager:github-pr-136-amd64

@jc21
Copy link
Member

jc21 commented May 8, 2019

Docker Image for build 4 is available on DockerHub as jc21/nginx-proxy-manager:github-pr-136-amd64

@jc21 jc21 merged commit 4fad9d6 into NginxProxyManager:develop May 8, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants