View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0019592 | Runner | Functions | Public | 2015-11-19 19:45 | 2019-01-04 16:23 |
Reporter | GameGeisha | Assigned To | Mike Dailly | ||
Priority | Medium | Severity | C - General | Reproducibility | 100% |
Status | Closed | Resolution | Fixed | ||
Product Version | 2.1.4 | ||||
Target Version | 2.2.1 | Fixed in Version | 2.2.1 | ||
Summary | 0019592: Functions: async_load[? 'status'] is wrong on a number of exports for when a request fails | ||||
Description | When a HTTP request fails, some exports incorrectly reports success through async_load[? 'status'] (i.e. giving it a value of 0). This can cause HTTP API integrations to attempt parsing failed responses instead of discarding them. | ||||
Steps To Reproduce | Attached is an example that makes a request to a non-existent URL. I've tested on Windows, Android and HTML5 so far, and here are the results: - On Windows, both http_get() and http_request() correctly reported -1 for failure. - On Android, both http_get() and http_request() incorrectly reported 0 for success when the HTTP status code is 404. - On HTML5, http_get() correctly reported -1 for failure, but http_request() incorrectly reported 0 for success. I suspect similar abnormalities on other exports (especially Mac and iOS), but I haven't personally tested those yet. | ||||
Tags | No tags attached. | ||||
1.4 Found In | |||||
2.x Runtime Found In | 2.1.4.218 | ||||
2.x Runtime Verified In | 2.2.1.268 | ||||
2015-11-19 19:45 Updater |
AndroidHTTPStatus.gmz (19,071 bytes) |
|
Will need to compile a full list of affected platforms. |
|
I believe this is fixed... reopen if not |
|
Reopening as the sample provided in the latest internal version still shows the issues in the original report |
2018-06-22 16:31 Developer |
|
|
fixed on red |