Open billthecatt opened 4 years ago
This stopped happening after I stopped the sniproxy.. what I don't get is why/how the steamcmd got into the habit of using ssl instead of http..
Not a good trend..
Ya something must have changed for the linux client, which is sad for me, because I use a linux scrip to preload and refresh the cache BEFORE the lan..
Anyway. I stopped steamcmd, and killed sniproxy, and boom, steamcmd worked. So i restarted steamcmd and it seems to default back to https on the next download.. So, for some reason https appears to be preferred over http?!?! this seems lame..
Didn't check that but: No chance to deny sniproxy listening on the domains?
Having an issue where my steamcmd (linux commandline) is using the sniproxy to download chunks of data instead of the cache:
2020-06-18 16:23:35 10.1.1.106:17227 -> 10.1.1.11:443 -> 162.254.195.30:443 [cache19-lax1.steamcontent.com] 899777/899777 bytes tx 1406/1406 bytes rx 1.834 seconds 2020-06-18 16:23:35 10.1.1.106:31933 -> 10.1.1.11:443 -> 162.254.195.15:443 [cache21-lax1.steamcontent.com] 560374/560374 bytes tx 1406/1406 bytes rx 1.785 seconds 2020-06-18 16:23:36 10.1.1.106:64589 -> 10.1.1.11:443 -> 162.254.195.24:443 [cache13-lax1.steamcontent.com] 864/864 bytes tx 1406/1406 bytes rx 0.443 seconds 2020-06-18 16:23:36 10.1.1.106:52379 -> 10.1.1.11:443 -> 162.254.195.24:443 [cache13-lax1.steamcontent.com] 1942/1942 bytes tx 1696/1696 bytes rx 0.643 seconds 2020-06-18 16:23:36 10.1.1.106:21121 -> 10.1.1.11:443 -> 162.254.195.43:443 [cache18-lax1.steamcontent.com] 683240/683240 bytes tx 1406/1406 bytes rx 2.182 seconds 2020-06-18 16:23:37 10.1.1.106:34243 -> 10.1.1.11:443 -> 162.254.195.15:443 [cache21-lax1.steamcontent.com] 363146/363146 bytes tx 1406/1406 bytes rx 1.240 seconds
Any ideas why it's going via SSL instead of via https?