Join GitHub today
GitHub is home to over 50 million developers working together to host and review code, manage projects, and build software together.
Sign upReplace ws-rs with async-tungstenite. #27164
Conversation
highfive
commented
Jul 3, 2020
|
Heads up! This PR modifies the following files:
|
| @@ -0,0 +1,3 @@ | |||
| [third-party-cookie-accepted.https.html] | |||
This comment has been minimized.
This comment has been minimized.
jdm
Jul 3, 2020
Author
Member
This new test failure shows up because tungstenite correctly passes through multiple Set-Cookie headers in the WS response, whereas ws-rs appears to silently drop all but the first.
|
r? @nox |
|
This looks cool! Will review on Monday! |
|
@bors-servo try=wpt |
Replace ws-rs with async-tungstenite. This change moves us from ws-rs (which doesn't see a lot of maintainer activity) and its custom async implementation to tungstenite and the tokio ecosystem. This is particularly important because of #27043, which breaks SSL websockets on Windows. Depends on sdroege/async-tungstenite#40. --- - [x] `./mach build -d` does not report any errors - [x] `./mach test-tidy` does not report any errors - [x] These changes fix #27043 - [x] There are tests for these changes
|
|
|
@bors-servo try=wpt |
Replace ws-rs with async-tungstenite. This change moves us from ws-rs (which doesn't see a lot of maintainer activity) and its custom async implementation to tungstenite and the tokio ecosystem. This is particularly important because of #27043, which breaks SSL websockets on Windows. Depends on sdroege/async-tungstenite#40. --- - [x] `./mach build -d` does not report any errors - [x] `./mach test-tidy` does not report any errors - [x] These changes fix #27043 - [x] There are tests for these changes
|
|
|
Ok, the test failures appear to be related to the host replacement that happens for WPT which confuses openssl. I need to figure out what we do differently in HTTPS code that allows it to work. |
|
@bors-servo try=wpt |
Replace ws-rs with async-tungstenite. This change moves us from ws-rs (which doesn't see a lot of maintainer activity) and its custom async implementation to tungstenite and the tokio ecosystem. This is particularly important because of #27043, which breaks SSL websockets on Windows. Depends on sdroege/async-tungstenite#40. --- - [x] `./mach build -d` does not report any errors - [x] `./mach test-tidy` does not report any errors - [x] These changes fix #27043 - [x] There are tests for these changes
|
|
|
@bors-servo retry |
Replace ws-rs with async-tungstenite. This change moves us from ws-rs (which doesn't see a lot of maintainer activity) and its custom async implementation to tungstenite and the tokio ecosystem. This is particularly important because of #27043, which breaks SSL websockets on Windows. Depends on sdroege/async-tungstenite#40. --- - [x] `./mach build -d` does not report any errors - [x] `./mach test-tidy` does not report any errors - [x] These changes fix #27043 - [x] There are tests for these changes
|
|
|
@bors-servo retry |
Replace ws-rs with async-tungstenite. This change moves us from ws-rs (which doesn't see a lot of maintainer activity) and its custom async implementation to tungstenite and the tokio ecosystem. This is particularly important because of #27043, which breaks SSL websockets on Windows. Depends on sdroege/async-tungstenite#40. --- - [x] `./mach build -d` does not report any errors - [x] `./mach test-tidy` does not report any errors - [x] These changes fix #27043 - [x] There are tests for these changes
|
|
|
@bors-servo retry |
|
|
jdm commentedJul 3, 2020
•
edited
This change moves us from ws-rs (which doesn't see a lot of maintainer activity) and its custom async implementation to tungstenite and the tokio ecosystem. This is particularly important because of #27043, which breaks SSL websockets on Windows.
Depends on sdroege/async-tungstenite#40.
./mach build -ddoes not report any errors./mach test-tidydoes not report any errors