-
Notifications
You must be signed in to change notification settings - Fork 41
Proxy not working correctly #25
Copy link
Copy link
Open
Description
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:
$ sha2 1.jpg
SHA-256 (1.jpg) = 6e667c6dc98d119f27bd58d95e6059b38c0504d2bffecfa8c91c56c33e16f118
$ ls -l@ 1.jpg
-rw-r--r--@ 1 me staff 487536 12 Feb 2018 1.jpg
Without proxy:
$ sha2 1.jpg.1
SHA-256 (1.jpg.1) = 309141024afd899bb30bad191af2c79b08968fc42be3f8707b9f3541a54c0c66
$ ls -l@ 1.jpg.1
-rw-r--r-- 1 me staff 270958 12 Feb 2018 1.jpg.1
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
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
No labels