ERROR: Connection timed out after 1001 milliseconds about pgsql-http HOT 7 CLOSED

Ok, I've found the following line in the http.c:
CURL_SETOPT(g_http_handle, CURLOPT_CONNECTTIMEOUT, 1);

So it seems it's hardcoded and not allowed to be changed at runtime.

from pgsql-http.

Ok, I've changed that line to:
CURL_SETOPT(g_http_handle, CURLOPT_CONNECTTIMEOUT_MS, g_timeout_msec);

It seems to be enough for the moment to bypass my connection issue.

from pgsql-http.

I bumped that value way down early in development of the extension because having your backend hang until the 5 minute time-out ended seemed bad (tm). I wonder if curl has an interrupt checker, that could be a good enhancement. In the meanwhile, adding this parameter to the new list of settable parameters seems wise.

from pgsql-http.

The timeout is user-configurable now with commits from #48

from pgsql-http.

It makes sense not to keep the 300s default value. However, thanks for adding it as a user-configurable parameter.

from pgsql-http.

Something weird.
In a function, I set the following options:
SET http.timeout_msec TO 5000;
PERFORM http_set_curlopt('CURLOPT_CONNECTTIMEOUT', '5');
PERFORM http_set_curlopt('CURLOPT_TIMEOUT_MS', '5000');
Then I run SELECT content INTO v_content FROM http_get('someurl');

But I still get the following error message:
Connection timed out after 1000 milliseconds

from pgsql-http.

It seems that each time http_get_handle() function is called, it resets the CURLOPT_CONNECTTIMEOUT to 1.
So curl_easy_setopt(handle, CURLOPT_CONNECTTIMEOUT, 1); should only be called once at initialization.

from pgsql-http.