Changelog
+Dan F (9 March 2007)
+- Updated the test harness to add a new "crypto" feature check and updated the
+ appropriate test case to use it. For now, this is treated the same as the
+ "SSL" feature because curl doesn't list it separately.
+
Daniel (9 March 2007)
- Robert Iakobashvili fixed CURLOPT_INTERFACE for IPv6.
be able to run (if these features are not present, the test will be
SKIPPED). Features testable here are:
+crypto
getrlimit
GnuTLS
idn
<server>
http
</server>
+<features>
+crypto
+</features>
<name>
HTTP with Digest authorization with stale=true
</name>
<server>
http
</server>
+<features>
+crypto
+</features>
<name>
HTTP PUT with --anyauth authorization (picking Digest)
</name>
<server>
http
</server>
+<features>
+crypto
+</features>
<name>
HTTP with proxy-requiring-Basic to site-requiring-Digest
</name>
<server>
http
</server>
+<features>
+crypto
+</features>
<name>
HTTP with proxy-requiring-Digest to site-requiring-Digest
</name>
<server>
http
</server>
+<features>
+crypto
+</features>
<name>
HTTP POST --digest to server not requiring any auth at all
</name>
<server>
http
</server>
+<features>
+crypto
+</features>
<name>
HTTP POST --digest to server doing a 302-location response
</name>
<server>
http
</server>
+<features>
+crypto
+</features>
<name>
HTTP proxy CONNECT auth Digest
</name>
<server>
http
</server>
+<features>
+crypto
+</features>
<name>
HTTP POST --digest
</name>
<server>
http
</server>
+<features>
+crypto
+</features>
<name>
HTTP POST --digest with server doing a 100 before 401 response
</name>
<server>
http
</server>
+<features>
+crypto
+</features>
<name>
HTTP POST multipart without Expect: header using proxy anyauth (Digest)
</name>
<server>
http
</server>
+<features>
+crypto
+</features>
<name>
HTTP POST multipart with Expect: header using proxy anyauth (Digest)
</name>
<server>
http
</server>
+<features>
+crypto
+</features>
<name>
HTTP with two Digest authorization headers
</name>
<server>
http
</server>
+<features>
+crypto
+</features>
<name>
HTTP with Digest authorization
</name>
<server>
http
</server>
+<features>
+crypto
+</features>
<name>
HTTP with Digest authorization with bad password
</name>
<server>
http
</server>
+<features>
+crypto
+</features>
<name>
HTTP with Digest *OR* Basic authorization
</name>
<server>
http
</server>
+<features>
+crypto
+</features>
<name>
HTTP PUT with Digest authorization
</name>
my $has_openssl; # set if libcurl is built with OpenSSL
my $has_gnutls; # set if libcurl is built with GnuTLS
my $has_nss; # set if libcurl is built with NSS
+my $has_crypto; # set if libcurl is built with cryptographic support
my $has_textaware; # set if running on a system that has a text mode concept
# on files. Windows for example
my @protocols; # array of supported protocols
if($feat =~ /SSL/i) {
# ssl enabled
$ssl_version=1;
+ # curl doesn't list cryptographic support separately, so treat
+ # it the same as SSL for the time being
+ $has_crypto=1;
}
if($feat =~ /Largefile/i) {
# large file support
next;
}
}
+ elsif($f eq "crypto") {
+ if($has_crypto) {
+ next;
+ }
+ }
# See if this "feature" is in the list of supported protocols
elsif (grep /^$f$/, @protocols) {
next;