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

DNS vs Reverse Proxy and /RAW/ #2224

Closed
ghost opened this issue Oct 15, 2019 · 2 comments
Closed

DNS vs Reverse Proxy and /RAW/ #2224

ghost opened this issue Oct 15, 2019 · 2 comments

Comments

@ghost
Copy link

ghost commented Oct 15, 2019

Hi!

I have described in details at #2214 and #2208 problems regarding /raw/. I think ZeroNet should not enforce headers and sandbox when /RAW/ is requested!

This will solve a lot of problems. Check this: #2208

@purplesyringa
Copy link
Contributor

@HelloZeroNet TBH this looks nonsense. Headers are required to forbid sites to access other sites. Can this be closed?

@HelloZeroNet
Copy link
Owner

I think it's better to have consistent security requirements.
I recommend to add the hosts to --ui_host or use apache/nginx to proxy the request

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