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

Origin not cached, all else is #61

Closed
JohnBFrm opened this issue Oct 5, 2019 · 9 comments
Closed

Origin not cached, all else is #61

JohnBFrm opened this issue Oct 5, 2019 · 9 comments
Labels
duplicate This issue or pull request already exists

Comments

@JohnBFrm
Copy link

JohnBFrm commented Oct 5, 2019

Describe the issue you are having

I am not seeing games on Origin picked up by the cache, but other services such as Steam and Blizzard's Battle.net app are cached as intended. This is in Stockholm, Sweden. Typical behavior for HTTPS traffic, but Origin shouldn't be downloading games over HTTPS?

How are you running the container(s)?

Exactly as per the readme except the location of the storage for the lancache container, since my host has it on /lancache and not /data.

DNS Configuration

The run command is directly from the readme. Device points at the host IP.

Output of container(s)

I'll happily dump any logs that you might need, just type out the path of them to me.
@unspec
Copy link
Member

unspec commented Oct 5, 2019

Sadly Origin is currently downloading games over HTTPS for the last few months - see uklans/cache-domains#98 for details, but that explains why you won't see it getting cached currently.

@JohnBFrm
Copy link
Author

JohnBFrm commented Oct 5, 2019

Thanks @unspec, I was looking around to see if something like that had been reported but didn't find anything.

@danielriddell21
Copy link

I have the same issue, has their been an update? I am running sniproxy, which is meant to convert HTTPs Traffic right?

@JohnBFrm
Copy link
Author

I have the same issue, has their been an update? I am running sniproxy, which is meant to convert HTTPs Traffic right?

No update as far as I know.
Sniproxy forwards HTTPS traffic since we have no insight in its payload, so we just forward it. This is the root of the issue and why we're hoping Origin will eventually not use HTTPS for their CDNs.

@VibroAxe
Copy link
Member

No official update we can give atm beyond nothing yet, watch this space

@danielriddell21
Copy link

Alright, sounds good. Thank you anyway

@plh1511
Copy link

plh1511 commented Dec 17, 2019

Am I understanding correctly that the sniproxy container doesn't help to cache Origin content? It just lets the Origin launcher function normally (without caching) while other services are being cached?

@JohnBFrm
Copy link
Author

Am I understanding correctly that the sniproxy container doesn't help to cache Origin content? It just lets the Origin launcher function normally (without caching) while other services are being cached?

Yes. The proxy simply allows us to pass HTTPS content as if there was no cache in place since there is nothing we can do with the encrypted payload.

@unspec
Copy link
Member

unspec commented Feb 22, 2020

Closing this issue - we are tracking Origins related efforts here: uklans/cache-domains#98

@unspec unspec closed this as completed Feb 22, 2020
@unspec unspec added the duplicate This issue or pull request already exists label Feb 22, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
duplicate This issue or pull request already exists
Projects
None yet
Development

No branches or pull requests

5 participants