dcv Posted 6 hours ago Report Posted 6 hours ago (edited) Hello, I was trying to use a proxy server in LoginSession. But for some reason I kept getting CONNECT 403 Forbidden. After confirming that in fact the proxy works on steamcommunity.com domain I started digging on what is the problem. And after couple of hours I found out that only requests to https://checkout.steampowered.com/login/settoken url in transfer_info field of finalizelogin endpoint response is getting forbidden whilst all of other domains work flawlessly. I'm not using any of those cookies for that checkout domain. Is it okay if I manually skip the finalization for this domain(by patching the package so it immediately returns if the domain matches?) Won't there be any problems with this? UPDATE: It seems that my proxy provider also blocking api.steampowered.com, so I might need to use a different provider. But still good to get an answer for the question above. Edited 6 hours ago by dcv UPDATE Quote
Dr. McKay Posted 5 hours ago Report Posted 5 hours ago If you aren't planning on making any requests to a domain, then you shouldn't have any issues patching the module to skip that domain's settoken call. Quote
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.