-
Notifications
You must be signed in to change notification settings - Fork 4
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
Implement GOG caching #3
Comments
Hey @Stealthii , did you ever receive a reply? |
Still nothing, contacted them twice in the past couple months. Will update if I hear anything! |
I also emailed them separately and got a generic "we've passed on your feedback" message, then nothing. On 21 July 2016 11:26:25 PM AEST, Stealthii [email protected] wrote:
|
@Stealthii Thanks for picking this up. The move to HTTPS from their side is only to be applauded, but seriously hampers our projects at the same time. We need to stay on top of this; I believe Akamai (among others) have started offering SSL CDNs on a large scale, so the situation is not going to improve. I believe Valve has the right idea in making it deliberately easy to cache their content (they encourage it, too). Hard to imagine GOG would want to be evil in this scenario, I'll try and get in touch with them, too. Cool project! |
GOG has recently moved to HTTPS for content delivery like Riot, and do not currently offer any downgrade facility for RFC1918 addresses.
I have contacted GOG's support team about possibly implementing this as a feature, but until then, this issue is blocked.
The text was updated successfully, but these errors were encountered: