We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
So when I'm using this trade URL : http://steamcommunity.com/tradeoffer/new/?partner=89031010&token=BqHjy99N, the offer can't be created because the script doesn't recognize it as a valid trade URL. Though you can clearly see it's working...
Am I getting something wrong or is it the verification process?
The text was updated successfully, but these errors were encountered:
I found what was wrong, it only works on HTTPS. Maybe it would be nice to also support HTTP?
Sorry, something went wrong.
I am pretty sure TradeURLs are only generated as HTTPs by Valve, that's why that check is in place.
2016-08-25 7:46 GMT-04:00 KowalskiThomas [email protected]:
I found what was wrong, it only works on HTTPS. Maybe it would be nice to also support HTTP? — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub #15 (comment), or mute the thread https://github.com/notifications/unsubscribe-auth/AFvii5hh4Ll7nwchIL_mT8iY2bCUsJz1ks5qjYCWgaJpZM4Js-qB .
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub #15 (comment), or mute the thread https://github.com/notifications/unsubscribe-auth/AFvii5hh4Ll7nwchIL_mT8iY2bCUsJz1ks5qjYCWgaJpZM4Js-qB .
No branches or pull requests
So when I'm using this trade URL : http://steamcommunity.com/tradeoffer/new/?partner=89031010&token=BqHjy99N, the offer can't be created because the script doesn't recognize it as a valid trade URL. Though you can clearly see it's working...
Am I getting something wrong or is it the verification process?
The text was updated successfully, but these errors were encountered: