-
Notifications
You must be signed in to change notification settings - Fork 527
[LTS] Kestrel considers Connection: keep-alive, upgrade
as non-upgrade request
#1171
Comments
Make sure to bump Hosting dependency to 1.0.1 once aspnet/Hosting#873 is in. |
This patch is approved, please ensure it is merged into the correct branch and building as part of the patch train. |
Was there a particular reason why we decided to port this to 1.0.2? A request with @anurse Did you repro the original issue on Kestrel 1.0.1? Do you know up to what version Firefox was sending |
I did not repro the original issue on 1.0.1, but neither did I try to repro it :). @BrennanConroy had the original repro. If the behavior is already correct in 1.0.1, I don't see a need to port the fix. As for which version of Firefox had the issue, I'm not sure. It's possible, given the fast pace of updates, they've changed it since @BrennanConroy originally reproduced it. |
I can check tomorrow |
Derp 😄 Let's see what happens here - it's easy to not check something in 😄 |
So 1.0.1 worked because it didn't even check for So 1.0.2 can probably stay as is. |
Alright I'm gonna close this then. |
Cool. Could we port the test over so we ensure that the behavior is never regressed? |
Agreed, @CesarBS could you port the test? Also the labels on this bug :) |
The tests added in #1178 were mostly unit tests that make ensure Kestrel's properly interprets the header in it's internal data structures. We need a new test verifying that it's possible to read all the data sent by the client over the upgraded connection given a |
👍 It looks like that should pass in 1.0.*. A functional test might be nice too. |
Ok so we're not fixing any product code, but we're just updating tests? |
@Eilon Correct. |
Ok, I'll remove it from my OneNote tracking page. Thanks! |
Removing the patch-approved label... |
Original issue: #1170.
We'll need to fix this in both 1.1.0 and 1.0.2 versions of Kestrel.
The text was updated successfully, but these errors were encountered: