curl/tests/data/test3102

<testcase>
<info>
<keywords>
HTTPS
HTTP GET
</keywords>
</info>

#
# Server-side
<reply>
<data>
</data>
</reply>

#
# Client-side
<client>
# SSL with libraries supporting CURLOPT_CERTINFO
<features>
SSL
!bearssl
!rustls
!wolfssl
</features>
<server>
https
</server>
<tool>
lib%TESTNUMBER
</tool>
<name>
verify certificate chain order with simple HTTPS GET
</name>
<command>
https://%HOSTIP:%HTTPSPORT/%TESTNUMBER
</command>
</client>

#
# Verify data after the test has been "shot"
<verify>
<protocol>
GET /%TESTNUMBER HTTP/1.1
Host: %HOSTIP:%HTTPSPORT
Accept: */*

</protocol>
</verify>
</testcase>
schannel: fix ordering of cert chain info - Use CERT_CONTEXT's pbCertEncoded to determine chain order. CERT_CONTEXT from SECPKG_ATTR_REMOTE_CERT_CONTEXT contains end-entity/server certificate in pbCertEncoded. We can use this pointer to determine the order of certificates when enumerating hCertStore using CertEnumCertificatesInStore. This change is to help ensure that the ordering of the certificate chain requested by the user via CURLINFO_CERTINFO has the same ordering on all versions of Windows. Prior to this change Schannel certificate order was reversed in 8986df80 but that was later reverted in f540a39b when it was discovered that Windows 11 22H2 does the reversal on its own. Ref: https://github.com/curl/curl/issues/9706 Closes https://github.com/curl/curl/pull/11632 2023-08-09 04:12:19 +08:00			`<testcase>`
			`<info>`
			`<keywords>`
			`HTTPS`
			`HTTP GET`
			`</keywords>`
			`</info>`

			`#`
			`# Server-side`
			`<reply>`
			`<data>`
			`</data>`
			`</reply>`

			`#`
			`# Client-side`
			`<client>`
			`# SSL with libraries supporting CURLOPT_CERTINFO`
			`<features>`
			`SSL`
			`!bearssl`
			`!rustls`
			`!wolfssl`
			`</features>`
			`<server>`
			`https`
			`</server>`
			`<tool>`
			`lib%TESTNUMBER`
			`</tool>`
tests: remove leading spaces from some tags The threee tags `<name>`, `</name>` and `<command>` were frequently used with a leading space that this removes. The reason this habbit is so widespread in testcases is probably that they have been copy and pasted. Hence, fixing them all now might curb this practice from now on. Closes #12028 2023-10-04 17:35:54 +08:00			`<name>`
schannel: fix ordering of cert chain info - Use CERT_CONTEXT's pbCertEncoded to determine chain order. CERT_CONTEXT from SECPKG_ATTR_REMOTE_CERT_CONTEXT contains end-entity/server certificate in pbCertEncoded. We can use this pointer to determine the order of certificates when enumerating hCertStore using CertEnumCertificatesInStore. This change is to help ensure that the ordering of the certificate chain requested by the user via CURLINFO_CERTINFO has the same ordering on all versions of Windows. Prior to this change Schannel certificate order was reversed in 8986df80 but that was later reverted in f540a39b when it was discovered that Windows 11 22H2 does the reversal on its own. Ref: https://github.com/curl/curl/issues/9706 Closes https://github.com/curl/curl/pull/11632 2023-08-09 04:12:19 +08:00			`verify certificate chain order with simple HTTPS GET`
tests: remove leading spaces from some tags The threee tags `<name>`, `</name>` and `<command>` were frequently used with a leading space that this removes. The reason this habbit is so widespread in testcases is probably that they have been copy and pasted. Hence, fixing them all now might curb this practice from now on. Closes #12028 2023-10-04 17:35:54 +08:00			`</name>`
			`<command>`
schannel: fix ordering of cert chain info - Use CERT_CONTEXT's pbCertEncoded to determine chain order. CERT_CONTEXT from SECPKG_ATTR_REMOTE_CERT_CONTEXT contains end-entity/server certificate in pbCertEncoded. We can use this pointer to determine the order of certificates when enumerating hCertStore using CertEnumCertificatesInStore. This change is to help ensure that the ordering of the certificate chain requested by the user via CURLINFO_CERTINFO has the same ordering on all versions of Windows. Prior to this change Schannel certificate order was reversed in 8986df80 but that was later reverted in f540a39b when it was discovered that Windows 11 22H2 does the reversal on its own. Ref: https://github.com/curl/curl/issues/9706 Closes https://github.com/curl/curl/pull/11632 2023-08-09 04:12:19 +08:00			`https://%HOSTIP:%HTTPSPORT/%TESTNUMBER`
			`</command>`
			`</client>`

			`#`
			`# Verify data after the test has been "shot"`
			`<verify>`
			`<protocol>`
			`GET /%TESTNUMBER HTTP/1.1`
			`Host: %HOSTIP:%HTTPSPORT`
			`Accept: /`

			`</protocol>`
			`</verify>`
			`</testcase>`