mirror of
https://github.com/curl/curl.git
synced 2026-04-13 00:31:41 +08:00
1fcf22585f
Setting `CURL_ENTROPY` in debug-enabled builds overrides the code paths responsible for random number generation. To avoid masking issue there, this patch moves `CURL_ENTROPY` settings to each test that requires it, and stop setting it by default for all tests (in `runner.pm`). This makes it possible to catch random generator issues in debug-enabled builds; extending test coverage. To keep offering a well-defined state for tests, make `runner.pm` delete the `CURL_ENTROPY` env, if present. Ref: #17970 Closes #17971
72 lines
1.2 KiB
Plaintext
72 lines
1.2 KiB
Plaintext
<testcase>
|
|
<info>
|
|
<keywords>
|
|
WebSockets
|
|
</keywords>
|
|
</info>
|
|
|
|
#
|
|
# Close connection during websocket upgrade
|
|
<reply>
|
|
<data nocheck="yes" nonewline="yes">
|
|
HTTP/1.1 101 Switching to WebSockets swsclose
|
|
Server: test-server/fake
|
|
Upgrade: websocket
|
|
Connection: Upgrade
|
|
Something: else
|
|
Sec-WebSocket-Accept: HkPsVga7+8LuxM4RGQ5p9tZHeYs=
|
|
|
|
</data>
|
|
# allow upgrade
|
|
<servercmd>
|
|
upgrade
|
|
</servercmd>
|
|
</reply>
|
|
|
|
#
|
|
# Client-side
|
|
<client>
|
|
# require Debug for the forced CURL_ENTROPY
|
|
<features>
|
|
Debug
|
|
ws
|
|
</features>
|
|
<setenv>
|
|
CURL_ENTROPY=12345678
|
|
</setenv>
|
|
<server>
|
|
http
|
|
</server>
|
|
<name>
|
|
WebSockets curl_ws_recv() with closed connection
|
|
</name>
|
|
<tool>
|
|
lib%TESTNUMBER
|
|
</tool>
|
|
<command>
|
|
ws://%HOSTIP:%HTTPPORT/%TESTNUMBER
|
|
</command>
|
|
</client>
|
|
|
|
#
|
|
# PONG with no data and the 32 bit mask
|
|
#
|
|
<verify>
|
|
<protocol nocheck="yes" crlf="yes">
|
|
GET /%TESTNUMBER HTTP/1.1
|
|
Host: %HOSTIP:%HTTPPORT
|
|
User-Agent: websocket/%TESTNUMBER
|
|
Accept: */*
|
|
Upgrade: websocket
|
|
Connection: Upgrade
|
|
Sec-WebSocket-Version: 13
|
|
Sec-WebSocket-Key: NDMyMTUzMjE2MzIxNzMyMQ==
|
|
|
|
</protocol>
|
|
|
|
# This test used to check that "connection closed" was output, but
|
|
# that is flaky since the outgoing PING just before might fail already
|
|
# and then the test exists before the output gets to be written
|
|
</verify>
|
|
</testcase>
|