Open tango-kilo opened 6 years ago
I have found that the sniproxy setup isn't perfect and some HTTPS traffic does not get passed through properly, sometimes causing problems like this one. I've been meaning to investigate further but I personally only use this project a couple of times a year and don't get much time to fix things.
In order to better debug these issues the sniproxy container will need better logging setup and the issue to be easily reproduced so that we can get a better idea of what's going wrong.
We used the cache yesterday for an event and it largely worked great, thank you for the work and making it available.
We ran into an issue with an attendee being unable to purchase Blizzard game content while behind the cache (D3 RoS). They were able to login and play just fine but when they tried to use the shop it would toss an error. Wasn't my machine so wasn't able to grab the blizzard code and was too long to remember.
Once again setting real DNS and flushing allowed it to work as expected. Any ideas on what to look at or adjust?
Thanks in advance.