-
Notifications
You must be signed in to change notification settings - Fork 1.6k
Description
Hello there!
Following the new release, I've been trying to build libwebsockets v4.4.1 with both AWS-LC and OpenSSL. I'm encountering consistent failures with the lws-minimal-secure-streams-testsfail test suite. Out of the 18 test cases that run, 2 fail consistently - both related to HTTP connections over port 80:
- h1:80 just get 200 (Test 1)
- h1:80 read bulk (Test 13)
Both tests expect a 200 OK response but instead timeout. I've verified this occurs with both AWS-LC and OpenSSL on my system (Ubuntu 24.04).
I noticed this commit changed httpbin to libwebsockets.org in several places. The httpbin service does respond with 200 OK over port 80, while libwebsockets.org redirects to HTTPS. I'm wondering if any of the following could be causing the failures:
- The test expects direct 200 responses over HTTP that are no longer available due to redirects
- I noticed the test name (ex. h1:80) and some comments in the test file reference port 80, but the configured port is 8080 - is that intentional?
- I'm missing some configuration step for the secure streams tests
I'd appreciate any guidance here on solving these test failures. I'm happy to provide additional details about my build environment or testing process if helpful. Thanks for your time!
Best,
Shubham
Possibly helpful screenshots:
- Redirect & Endpoints tested with curl
- Test fail logs (with AWS-LC, although they look the same with OpenSSL)
- Test failure with OpenSSL