Date: 19 April 1999
Author: Daniel Stenberg <Daniel.Stenberg@sth.frontec.se>


             Frequently Asked Questions about Curl
             =====================================


1. "@SHELL@: Command not found"

  This problem is known to occur at times, most often on Linux boxes 
  actually since they use to have the tools involved installed.

     gcc -DHAVE_CONFIG_H -I. -I. -I..     -g -O2 -c base64.c
     make[2]: @SHELL@: Command not found

  This problem is happening because of some odd combination of 'autoconf'
  and 'automake', both used if found when building curl. There are two good
  fixes for this problem:

  A. Make sure the configure script doesn't find 'autoconf' and 'automake'
     in the path when it runs.

  B. Update 'autoconf' and 'automake' to newer versions.

2. Problems connecting to SSL servers.

  It took a very long time before I could sort out why curl had problems
  to connect to certain SSL servers when using SSLeay or OpenSSL v0.9+.
  The error sometimes showed up similar to:

  16570:error:1407D071:SSL routines:SSL2_READ:bad mac decode:s2_pkt.c:233:

  It turned out to be because many older SSL servers don't deal with SSLv3
  requests properly. To correct this problem, either upgrade to a newer
  release of curl that will let you select SSLv2 from the command line, or
  patch your curl source to use SSLv2_client_method() instead of the
  function call used before, SSLv23_client_method().

3. "curl: too big header"

  In curl 5.5 and earlier, curl was built with a 512 byte HTTP header size
  limit. If a single header line was read in several sequential reads, curl
  used a buffer this big to create it in.

  In the earlier curl 5.6 betas, the limit was raised to 2048 bytes.

  In later curl 5.6 betas, it will be turned into a dynamicly reallocatable
  buffer and this problem should not be able to occur again!

  To make older curl versions deal with longer headers, edit the HEADERSIZE
  #define in the source and recompile.
