Thanks for trying the libtool upgrade. If you can give 1.5 a try when it's out and see what happens, I'll appreciate it!

Here's my perl:
  $ perl -v
  This is perl, v5.6.1 built for cygwin-multi

Tests 500 and 503 by themselves are OK. 504 fails even by itself.

  $ ./runtests.pl -d -k -v 504
  test 504...[simple multi through local proxy without listener]
  ./libtest/lib504 http://127.0.0.1:8433/504 localhost:55555 \
>log/stdout504 2>log/
  stderr504
  curl returned 0, 100 was expected
   error FAILED

  $ cat log/stderr504
  URL: http://127.0.0.1:8433/504
  * About to connect() to localhost:55555
  not reached!
  * Closing connection #0

The pairs:
 190 500 fails.
 190 503 fails.
 138 500 also fails.

  58 500 works.
 202 500 works.
 501 500 works.
 502 503 works.

Here's the 190/500 combination:

  $ ./runtests.pl -d -k -v 190 500
  [190 output snipped...]
  No server running, start it
  CMD: perl -I. ./httpserver.pl -v 8999 &
  *** cURL test suite HTTP server/0.1 listening on port 8999 ***
  test 500...[simple libcurl HTTP GET tool]
  ./libtest/lib500 http://127.0.0.1:8999/500 >log/stdout500 2>log/stderr500
   data OK0a1,5
> GET /500 HTTP/1.1
> Host: 127.0.0.1:8999
> Pragma: no-cache
> Accept: image/gif, image/x-xbitmap, image/jpeg, image/pjpeg, */*
>
   protocol FAILED

  $ cat log/stdout500
  HTTP/1.1 200 OK
  Date: Thu, 09 Nov 2010 14:49:00 GMT
  Server: test-server/fake
  Last-Modified: Tue, 13 Jun 2000 12:10:00 GMT
  ETag: "21025-dc7-39462498"
  Accept-Ranges: bytes
  Content-Length: 6
  Connection: close
  Content-Type: text/html
  Funny-head: yesyes

  <foo>

  $ cat log/stderr500
  URL: http://127.0.0.1:8999/500

And when it works:

  $ ./runtests.pl -d -k -v 500
  No server running, start it
  CMD: perl -I. ./httpserver.pl -v 8999 &
  *** cURL test suite HTTP server/0.1 listening on port 8999 ***
  test 500...[simple libcurl HTTP GET tool]
  ./libtest/lib500 http://127.0.0.1:8999/500 >log/stdout500 2>log/stderr500
   data OK protocol OK

Note: in this case, the stdout and stderr files appear identical.

This looks pretty normal to me, so I'm not sure what else to look at.
But it does seem to only fail after running an FTP server...

- Kevin

-----Original Message-----
From: Daniel Stenberg [mailto:daniel_at_haxx.se]
Sent: Friday, March 14, 2003 10:20 AM

On Fri, 14 Mar 2003, Roth, Kevin P. wrote:
> test 500... protocol FAILED
> test 501...OK
> test 502...OK
> test 503... protocol FAILED
> test 504... error FAILED
> TESTDONE: 93 tests out of 96 reported OK: 96%
> TESTFAIL: These test cases failed: 500 503 504

Strange. Can you run these tests stand-alone and see what they say:

-------------------------------------------------------
This SF.net email is sponsored by:Crypto Challenge is now open!
Get cracking and register here for some mind boggling fun and
the chance of winning an Apple iPod:
http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0031en
Received on 2003-03-14