Daniel Stenberg 74851340bd PROXYHEADER: send these headers in "normal" proxy requests too
Updated the docs to clarify and the code accordingly, with test 1528 to
verify:

When CURLHEADER_SEPARATE is set and libcurl is asked to send a request
to a proxy but it isn't CONNECT, then _both_ header lists
(CURLOPT_HTTPHEADER and CURLOPT_PROXYHEADER) will be used since the
single request is then made for both the proxy and the server.
2014-04-04 17:03:43 +02:00
..
2010-04-14 17:34:57 +02:00
2013-01-13 23:16:11 +01:00
2013-08-06 14:12:45 +02:00
2014-04-04 17:03:43 +02:00
2014-03-14 23:38:00 +01:00
2014-03-14 23:38:00 +01:00
2013-04-23 21:41:38 +02:00
2014-03-14 23:38:00 +01:00
2014-03-17 20:48:06 +01:00
2014-03-14 23:38:00 +01:00
2014-03-14 23:38:00 +01:00
2014-01-07 23:51:01 +01:00
2011-12-30 03:53:25 +01:00
2014-03-14 23:38:00 +01:00
2010-02-14 19:40:18 +00:00
2010-04-19 11:16:30 +02:00
2014-03-14 23:38:00 +01:00
2014-03-14 23:38:00 +01:00
2014-03-14 23:38:00 +01:00

                                  _   _ ____  _
                              ___| | | |  _ \| |
                             / __| | | | |_) | |
                            | (__| |_| |  _ <| |___
                             \___|\___/|_| \_\_____|

README.win32

  Read the README file first.

  Curl has been compiled, built and run on all sorts of Windows and win32
  systems. While not being the main develop target, a fair share of curl users
  are win32-based.

  The unix-style man pages are tricky to read on windows, so therefore are all
  those pages converted to HTML as well as pdf, and included in the release
  archives.

  The main curl.1 man page is also "built-in" in the command line tool. Use a
  command line similar to this in order to extract a separate text file:

        curl -M >manual.txt

  Read the INSTALL file for instructions how to compile curl self.