There seems to be some inconsistencies on how the result is returned between Windows, Linux cURL backend, and Linux OpenSSL backend.
Case 1: https.request("http://site_that_gives_timeout")) and https.request("http://invalid.hostname")
With Windows and Linux OpenSSL backend, all of those return 400 status code. Linux with cURL backend return 0 status code.
Case 2: https.request("htt://invalid.protocol")
With Windows and Linux OpenSSL backend, Lua 5.1 crashes while LuaJIT prints C++ exception thanks to LuaJIT exception interoperability. Linux cURL backend returns 0.
There seems to be some inconsistencies on how the result is returned between Windows, Linux cURL backend, and Linux OpenSSL backend.
Case 1:
https.request("http://site_that_gives_timeout"))andhttps.request("http://invalid.hostname")With Windows and Linux OpenSSL backend, all of those return 400 status code. Linux with cURL backend return 0 status code.
Case 2:
https.request("htt://invalid.protocol")With Windows and Linux OpenSSL backend, Lua 5.1 crashes while LuaJIT prints
C++ exceptionthanks to LuaJIT exception interoperability. Linux cURL backend returns 0.