HTTP Request Successful Parameter

Dr. McKay · **Author**

Under what conditions would the requestSuccessful param in the HTTP request callback be false?

asherkin · 03-03-2013 , 10:38 Re: HTTP Request Successful Parameter

It couldn't connect to the server.

Dr. McKay · 03-03-2013 , 10:53 HTTP Request Successful Parameter

Quote:

Originally Posted by asherkin

It couldn't connect to the server.

I have been reported incidents where a status code of 200 has been returned but requestSuccessful was false. Why would this happen?

asherkin · *Last edited by asherkin; 03-03-2013 at 11:00.*

Quote:

Originally Posted by Dr. McKay

I have been reported incidents where a status code of 200 has been returned but requestSuccessful was false. Why would this happen?

Not a clue. EDIT: Maybe pulling from cache?

Dr. McKay · 03-03-2013 , 11:23 HTTP Request Successful Parameter

Quote:

Originally Posted by asherkin

Not a clue. EDIT: Maybe pulling from cache?

That's all I can figure. I think something weird happened yesterday with SteamTools but I can't figure what. My backpack.tf plugin started failing yesterday when downloading from backpack.tf (requestSuccessful false, status code occasionally 200 but usually 0), but the guy who runs the site didn't notice any downtime. Rather, be told me that his API started getting slammed, which was causes by the plugin on various servers attempting to retry.

A single other person reported the same thing for my SteamRep plugin, but as far as I can tell, he was the only person this happened to. He reloaded SteamTools and it started working again.

psychonic · 03-03-2013 , 18:23 Re: HTTP Request Successful Parameter

Quote:

Originally Posted by Dr. McKay

That's all I can figure. I think something weird happened yesterday with SteamTools but I can't figure what. My backpack.tf plugin started failing yesterday when downloading from backpack.tf (requestSuccessful false, status code occasionally 200 but usually 0), but the guy who runs the site didn't notice any downtime. Rather, be told me that his API started getting slammed, which was causes by the plugin on various servers attempting to retry.

A single other person reported the same thing for my SteamRep plugin, but as far as I can tell, he was the only person this happened to. He reloaded SteamTools and it started working again.

SteamTools just passes on the param values from steam itself, and I think I've had this same case happen when using ISteamHTTP directly (the http code 200 but request not successful). I ended up just checking both.