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

Implement GOG caching #3

Open
Stealthii opened this issue May 11, 2016 · 4 comments
Open

Implement GOG caching #3

Stealthii opened this issue May 11, 2016 · 4 comments

Comments

@Stealthii
Copy link
Contributor

Stealthii commented May 11, 2016

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.

Hi GOG team!

I help prove tech support and services for a local gaming society, who also run a large gaming and anime convention once a year. We hit 5000 attendees but survive with only an 8Mbit internet connection.

More recently, we've rolled out CDN caching on-site for many known game services, including Riot, PSN, Steam, etc. This has enabled us to allow (rather than block) these services as we have limited bandwidth available.

Riot recently moved to HTTPS for content delivery like you guys, but in order to help local LAN parties cache, they gracefully fallback to HTTP when (e.g. cdn.gog.com) resolves to an RFC1918 (or local) address.

It would be great if you could add this feature - right now there are a few games people play that are available on GOG but we have had to block this due to inadequate bandwidth, requiring people to have the game installed from home before they come.

Discussion on Riot's change: ti-mo/ansible-lanparty#8 (comment)

Q-Con's qcacher: https://github.com/Q-Con/qcacher

Best Regards,
Dan Porter

@sirsquidness
Copy link

Hey @Stealthii , did you ever receive a reply?

@Stealthii
Copy link
Contributor Author

Still nothing, contacted them twice in the past couple months. Will update if I hear anything!

@sirsquidness
Copy link

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:

Still nothing, contacted them twice in the past couple months. Will
update if I hear anything!


You are receiving this because you commented.
Reply to this email directly or view it on GitHub:
#3 (comment)

@ti-mo
Copy link

ti-mo commented Jul 29, 2016

@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!

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

3 participants