Thank you for this extension! I've noticed that sometimes a timeout setting seems to be ignored, and I think what's happening is that only the second SET matters.
The following runs successfully, even though the response isn't coming back from Google in 1ms:
SET http.curlopt_timeout_ms TO 1;
SELECT * FROM http_get('https://google.com');You can repeatedly run the http_get line and it will keep working, obviously ignoring the timeout. But run the SET again and suddenly it will start failing as intended. From that point it will continue failing until you disconnect and reconnect.
Note that this applies only to SET. http_set_curlopt() works as expected, presumably because it initializes the global http handler.
Thank you for this extension! I've noticed that sometimes a timeout setting seems to be ignored, and I think what's happening is that only the second
SETmatters.The following runs successfully, even though the response isn't coming back from Google in 1ms:
You can repeatedly run the
http_getline and it will keep working, obviously ignoring the timeout. But run theSETagain and suddenly it will start failing as intended. From that point it will continue failing until you disconnect and reconnect.Note that this applies only to
SET.http_set_curlopt()works as expected, presumably because it initializes the global http handler.