- 18 Sep, 2010 4 commits
-
-
Daniel Stenberg authored
When it returns 0 it means no timeout. Only a negative value means that we're out of time.
-
Daniel Stenberg authored
If built without HTTP or proxy support it would cause a compiler warning due to the unused variable. I moved the declaration of it into the only scope it is used.
-
Tor Arntsen authored
bool_false is the internal name used in the setup_once.h definition we fall back to for non-C99 non-stdbool systems, it's not the actual name to use in assignments (we use bool_false, bool_true there to avoid global namespace problems, see comment in setup_once.h). The correct C99 value to use is 'false', but let's use FALSE as used elsewhere when assigning to bits.close. FALSE is set equal to 'false' in setup_once.h when possible. This fixes a build problem on C99 targets.
-
Tor Arntsen authored
-
- 17 Sep, 2010 3 commits
-
-
Mauro Iorio authored
As of curl-7.21.1 tunnelling ldap queries through HTTP Proxies is not supported. Actually if --proxytunnel command-line option (or equivalent CURLOPT_HTTPPROXYTUNNEL) is used for ldap queries like ldap://ldap.my.server.com/... You are unable to successfully execute the query. In facts ldap_*_bind is executed directly against the ldap server and proxy is totally ignored. This is true for both openLDAP and Microsoft LDAP API. Step to reproduce the error: Just launch "curl --proxytunnel --proxy 192.168.1.1:8080 ldap://ldap.my.server.com/dc=... " This fix adds an invocation to Curl_proxyCONNECT against the provided proxy address and on successful "CONNECT" it tunnels ldap query to the final ldap server through the HTTP proxy. As far as I know Microsoft LDAP APIs don't permit tunnelling in any way so the patch provided is for OpenLDAP only. The patch has been developed against OpenLDAP 2.4.23 and has been tested with Microsoft ISA Server 2006 and works properly with basic, digest and NTLM authentication.
-
Daniel Stenberg authored
Rodric provide an awesome recipe that proved libcurl didn't timeout at the requested time - it instead often timed out at [connect time] + [timeout time] instead of the documented and intended [timeout time] only. This bug was due to the code using the wrong base offset when comparing against "now". I could also take the oppurtinity to simplify the code by properly using of the generic help function for this: Curl_timeleft. Reported by: Rodric Glaser Bug: http://curl.haxx.se/bug/view.cgi?id=3061535
-
Daniel Stenberg authored
As this function uses return code 0 to mean that there is no timeout, it needs to check that it doesn't return a time left value that is exactly zero. It could lead to libcurl doing an extra 1000 ms select() call and thus not timing out as accurately as it should. I fell over this bug when working on the bug 3061535 but this fix does not correct that problem alone, although this is a problem that needs to be fixed. Reported by: Rodric Glaser Bug: http://curl.haxx.se/bug/view.cgi?id=3061535
-
- 16 Sep, 2010 2 commits
-
-
Daniel Stenberg authored
if ( => if( while ( => while( and some other changes in the similar spirit, trying to make the whole file use the same style
-
Daniel Stenberg authored
-
- 15 Sep, 2010 1 commit
-
-
James Bursa authored
-
- 14 Sep, 2010 2 commits
-
-
James Bursa authored
1. Remove the comment warning that it's "not been verified to work". It works with no problems in my testing. 2. Remove 2 unnecessary includes. 3. Remove the myrealloc(). Initialize chunk.memory with malloc() instead of NULL. The comments for these two parts contradicted each other. 4. Handle out of memory from realloc() instead of continuing. 5. Print a brief status message at the end.
-
Daniel Stenberg authored
The timeout is set for the connect phase already at the start of the request so we should not add a new one, and we MUST not set expire to 0 as that will remove any other potentially existing timeouts.
-
- 12 Sep, 2010 6 commits
-
-
Peter Pentchev authored
-
Daniel Stenberg authored
-
Daniel Stenberg authored
-
Daniel Stenberg authored
-
Daniel Stenberg authored
-
Dan Fandrich authored
When curl calls a function from that library then it needs to explicitly link to the library instead of piggybacking on libcurl's own dependency. Without this, GNU ld with the --no-add-needed flag fails when linking (which Fedora now does by default). Reported by: Quanah Gibson-Mount Bug: http://curl.haxx.se/mail/lib-2010-09/0085.html
-
- 09 Sep, 2010 2 commits
-
-
Dan Fandrich authored
-
Tor Arntsen authored
Use %HOSTIP:%HTTPPORT instead of 127.0.0.1:8990 so that verification works if the baseport change option is used when executing runtests.pl.
-
- 08 Sep, 2010 2 commits
-
-
Daniel Stenberg authored
-
Daniel Stenberg authored
Clarified as it isn't used with a -D option for them. Reported by: Artfunkel Bug: http://curl.haxx.se/bug/view.cgi?id=3060381
-
- 07 Sep, 2010 2 commits
-
-
Daniel Stenberg authored
Added "3.19 How do I get HTTP from a host using a specific IP address?" and updated some stuff about certs etc.
-
Daniel Stenberg authored
The code reading chunked encoding attempts to rewind the code if it had read more data than the chunky parser consumes. The rewinding can fail and it will then cause an error. This change now makes the rewinding only happen if pipelining is in use - as that's the only time it really needs to be done. Bug: http://curl.haxx.se/mail/lib-2010-08/0297.html Reported by: Ron Parker
-
- 06 Sep, 2010 2 commits
-
-
Kamil Dudka authored
-
Kamil Dudka authored
-
- 05 Sep, 2010 2 commits
-
-
Daniel Stenberg authored
-
Daniel Stenberg authored
Curl_getconnectinfo() is changed to return a proper curl_socket_t for the last socket so that it'll work more portably (and cause less compiler warnings).
-
- 03 Sep, 2010 2 commits
-
-
Guenter Knauf authored
-
Dan Fandrich authored
Otherwise, there could be problems running in certain locales.
-
- 02 Sep, 2010 1 commit
-
-
Guenter Knauf authored
-
- 01 Sep, 2010 6 commits
-
-
Guenter Knauf authored
-
Guenter Knauf authored
Adam Light posted this patch to the list which enables builds from git with VC versions other than vc6; also he added a vc10 target.
-
Guenter Knauf authored
-
Daniel Stenberg authored
Add a timeout check for handles in the state machine so that they will timeout in all states disregarding what actions that may or may not happen. Fixed a bug in socket_action introduced recently when looping over timed out handles: it wouldn't assign the 'data' variable and thus it wouldn't properly take care of handles. In the update_timer function, the code now checks if the timeout has been removed and then it tells the application. Previously it would always let the remaining timeout(s) just linger to expire later on.
-
Daniel Stenberg authored
Curl_expire() set to 0 expires ALL timeouts so it should only be called if we truly and really want to remove all timeouts for the handle.
-
Daniel Stenberg authored
Make use of the helper function Curl_timeleft() instead of duplicating code.
-
- 30 Aug, 2010 2 commits
-
-
Daniel Stenberg authored
Each easy handle has a list of timeouts, so as soon as the main timeout for a handle expires, we must make sure to get the next entry from the list and re-add the handle to the splay tree. This was attempted previously but was done poorly in my commit 232ad654.
-
Dan Fandrich authored
-
- 28 Aug, 2010 1 commit
-
-
Daniel Stenberg authored
When a new transfer is about to start we now set the proper timeouts to expire for the multi interface if they are set for the handle. This is a follow-up bugfix to make sure that easy handles timeout properly when the times expire and the multi interface is used. This also improves curl_multi_timeout().
-