Steam may be using HTTPS for CDN

[uklans]

Steam may be using HTTPS for CDN

[VibroAxe]

We are aware that steam is a mixed content engine now. Running the SniProxy is the correct resolution to this, unfortunately there is no way at present to enable us to cache anything which is transferred over https.

Can you clarify if you think the logging on your steamcache is broken, or if you think that you are no longer seeing any traffic at all to the steam cache? We usually see a mix of traffic on steam hitting both the cache and the sniproxy

[sirsquidness]

You should experiment with rejecting the https CDN hostnames in sniproxy. Steam should then try other CDN sources, hopefully trying a plain text http one instead. I don't get any https sources here, so I can't test easily.

…

On 8 November 2018 6:57:23 pm AEDT, James Kinsman ***@***.***> wrote: We are aware that steam is a mixed content engine now. Running the SniProxy is the correct resolution to this, unfortunately there is no way at present to enable us to cache anything which is transferred over https. Can you clarify if you think the logging on your steamcache is broken, or if you think that you are no longer seeing any traffic at all to the steam cache? We usually see a mix of traffic on steam hitting both the cache and the sniproxy -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: #40 (comment)

[VibroAxe]

@sirsquidness one of the things on the list to try, we'll hopefully make some progress on this in the next few weeks with stratlan and epic.lite coming up with some time to tinker

[VibroAxe]

@shinji257 can you pull the latest steamcache image and then run some steam downloads with --env BEAT_TIME 1m, then upload your /data/logs/access.log for the steam container please

[shinji257]

Sorry. I was looking for this post previously to let you know we had come up with a resolution.

I had it set as primary but the router's own DNS was set as secondary (the upstream for steamcache-dns was set there too). Seems that for some reason the systems were using the secondary DNS. I changed our network config to have the router use steamcache-dns as upstream then point steamcache-dns to a public dns from there for its upstream. After that it worked fine using primarily http sources.

[VibroAxe]

glad you got it sorted