-
Notifications
You must be signed in to change notification settings - Fork 37
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
Proxy not working correctly #25
Comments
Thanks for this, interesting, I'll take a look - or feel free to submit a PR fix :) |
I've been able to get it working with nginx, technically you can simply replace your code with that also 😁 default.conf:
Dockerfile:
working perfectly for me. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hey, after running the docker image and testing the proxy, the transferred data is unfortunately corrupted and also missing the CORS headers (maybe because of the data corruption, as the chrome console tells me about an unexpected end of file).
Regarding data integrity, tested with this random cat pic: https://www.tierfreund.de/wp-content/uploads/2016/09/1.jpg
With proxy:
Without proxy:
Maybe I did something wrong?
Edit: There seems to be an issue with image data, it can be recreated by looking at https://cors-container.herokuapp.com/https://google.com
The text was updated successfully, but these errors were encountered: