![flashcode 2035 httpstatus 0 flashcode 2035 httpstatus 0](http://aucimages.jdmvip.com/2001_MITSUBISHI_GALANT_VR_4V_EC5A-4rDculWQalcxjO-2035/2001_MITSUBISHI_GALANT_VR_4V_EC5A-4rDculWQalcxjO-2035-2-large.jpg)
![flashcode 2035 httpstatus 0 flashcode 2035 httpstatus 0](http://forums.encoreusa.com/upfiles/5151/56FDDFE3F4C4424AA488B5A5425C5F72.jpg)
Privacy policy Back to safety This server could not prove that it is (for example, passwords, messages, or credit cards).Īutomatically report details of possible security incidents to Google. That call is made from windows task that calls a VBS file, so to troubleshoot the problem, pointed a browser to the url and we get a Privacy Error:Īttackers might be trying to steal your information from localhost But it is apparently used in cases where the client needs to maintain an active socket connection to the server, and the server is waiting on the client to send more data over the open socket, but it doesn't in a given amount of time and the server ends the connection with a 408 status code, essentially telling the client "you took too long". HTTP status 408 is pretty uncommon in my experience.
#FLASHCODE 2035 HTTPSTATUS 0 CODE#
Note that in cases where the status code is 0, the real error is captured in the returned NSError object, not the NSHTTPURLResponse. However, it will still fail with an apparent status code of 0. Usually in the case of the latter though the phone is smart enough to know it doesn't have a network connection and will fail immediately. The timeout itself could be for various reasons, such as the server simply not responding in time, being blocked by a firewall, or your entire network connection being down. In your case, you are appearing to get a status code of 0 because the request is timing out and 0 is just the default value for the property. The server will never return a status of 0 as this is not a valid HTTP status code. A status code of 0 in an NSHTTPURLResponse object generally means there was no response, and can occur for various reasons.