Skip to content
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

Issues with proxy_pass #39

Open
isklikas opened this issue Feb 28, 2017 · 2 comments
Open

Issues with proxy_pass #39

isklikas opened this issue Feb 28, 2017 · 2 comments

Comments

@isklikas
Copy link

Basically, I use nginx to forward homebridge-server (with HTTPS and username / password authentication), so that I can have remote access, as my setup is a headless Ubuntu Server. However I found that when setting the "add_header X-Content-Type-Options nosniff;" header, the proxy pass, now returns the page as raw HTML. Commenting out this line fixes this issue, but since I also happen to host a Wordpress on my server (on a different domain of course), this line is very important to me...

@isklikas
Copy link
Author

Update: The reason behind this is fairly simple. This line prevents MIME-sniffing a response away from the declared content-type as the header instructs the browser not to override the response content type. With the nosniff option, if the server says the content is text/html, the browser will render it as text/html

@maplesteve
Copy link

maplesteve commented Feb 28, 2017

Thanks for reporting. This will be fixed in an upcoming version.
(@gismo141 the v2 branch has correct headers for the content type)

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

No branches or pull requests

2 participants