Files
curl/lib
Steve Holme 0c762f1c92 pop3: Fixed auth preference not being honored when CAPA not supported
If a user indicated they preferred to authenticate using APOP or a SASL
mechanism, but neither were supported by the server, curl would always
fall back to clear text when CAPA wasn't supported, even though the
user didn't want to use this.

This also fixes the auto build failure caused by commit 6f2d5f0562.
2013-12-24 22:49:36 +00:00
..
2013-03-07 11:08:05 +01:00
2013-02-14 10:41:45 +01:00
2013-02-14 10:41:45 +01:00
2012-07-05 22:18:11 +02:00
2013-04-26 22:55:55 +02:00
2013-04-26 22:55:55 +02:00
2013-09-17 23:25:56 +02:00
2013-12-20 17:12:42 +01:00
2013-12-20 17:12:42 +01:00
2013-10-30 11:12:06 +01:00
2013-09-10 23:18:43 +02:00
2013-09-10 23:18:43 +02:00
2013-09-07 11:28:12 +02:00
2013-12-20 17:12:42 +01:00
2013-11-03 10:17:26 +00:00
2013-04-10 16:44:54 +02:00
2013-09-10 20:27:52 +01:00
2011-04-16 00:11:43 +02:00
2013-08-31 19:12:35 +02:00
2013-12-11 16:32:21 +01:00
2013-03-14 13:30:59 +01:00
2013-12-20 17:12:42 +01:00
2013-10-28 12:00:22 +01:00
2013-07-12 12:11:11 +02:00
2013-12-20 17:12:42 +01:00
2013-12-20 17:12:42 +01:00
2013-02-14 10:41:45 +01:00
2013-02-14 10:41:45 +01:00
2013-08-20 23:13:19 +02:00
2013-02-01 08:14:46 +01:00
2013-12-20 17:12:42 +01:00
2013-02-01 08:14:46 +01:00
2013-10-30 11:12:06 +01:00

HTTP Pipelining with libcurl
============================

Background

Since pipelining implies that one or more requests are sent to a server before
the previous response(s) have been received, we only support it for multi
interface use.

Considerations

When using the multi interface, you create one easy handle for each transfer.
Bascially any number of handles can be created, added and used with the multi
interface - simultaneously. It is an interface designed to allow many
simultaneous transfers while still using a single thread. Pipelining does not
change any of these details.

API

We've added a new option to curl_multi_setopt() called CURLMOPT_PIPELINING
that enables "attempted pipelining" and then all easy handles used on that
handle will attempt to use an existing pipeline.

Details

- A pipeline is only created if a previous connection exists to the same IP
  address that the new request is being made to use.

- Pipelines are only supported for HTTP(S) as no other currently supported
  protocol has features resemembling this, but we still name this feature
  plain 'pipelining' to possibly one day support it for other protocols as
  well.

- HTTP Pipelining is for GET and HEAD requests only.

- When a pipeline is in use, we must take precautions so that when used easy
  handles (i.e those who still wait for a response) are removed from the multi
  handle, we must deal with the outstanding response nicely.

- Explicitly asking for pipelining handle X and handle Y won't be supported.
  It isn't easy for an app to do this association. The lib should probably
  still resolve the second one properly to make sure that they actually _can_
  be considered for pipelining. Also, asking for explicit pipelining on handle
  X may be tricky when handle X get a closed connection.