1940663 - NS_ERROR_NET_RESET on POST

Status: RESOLVED FIXED

(Core :: Networking, defect, P2)

Description

[mspclaims]

Attachment: Screenshot 2025-01-08 223533.png

User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/131.0.0.0 Safari/537.36

Steps to reproduce:

Attempt to login to https://my.claimmanager.ca - two setp process, first step username, second - password. Both requests go to same backend URL

Actual results:

Second POST requests (with correct password) result in status code 200 and response body visible on Network tab in Dev Tools, but also NS_ERROR_NET_RESET error which prevents user from logging in.
See attached screenshot

Expected results:

Same steps in Chrome or Edge allow user to proceed.

This is production site so I cannot provide username/password.
Server sends `Connection: keep-alive'
Server is IIS10, connection in http/2
Same FE connected to backend on IIS7.5 works fine in Firefox (http/1.1)
I'm available to chat and share screen if needed.

Comment 1

[BugBot [:suhaib / :marco/ :calixte]]

The Bugbug bot thinks this bug should belong to the 'Toolkit::Password Manager' component, and is moving the bug to that component. Please correct in case you think the bot is wrong.

Comment 2

[mspclaims]

Attachment: dev tool shows response from server

Comment 3

[mspclaims]

no this is not related to password management.

Comment 4

[Kershaw Chang [:kershaw]]

Hi Reporter,

NS_ERROR_NET_RESET usually indicates the server has reset the connection, not Firefox.
In order to help us debug this, could you try to capture a http log or a wireshark trace?
You could send the logs to [e-mail] to ensure that the information remains secure.

Thanks.

Comment 5

[mspclaims]

Thanks for reply. I collected logs and sent to email above.

Comment 6

[Kershaw Chang [:kershaw]]

Thanks for the log.
It shows that the h2 connection was reset by the server with HTTP_1_1_REQUIRED error.

2025-01-23 02:56:18.025000 UTC - [Parent 28304: Socket Thread]: I/nsHttp Http2Session::RecvRstStream 21650110700 RST_STREAM Reason Code 13 ID 65

However, this happens after Firefox receives the HTTP response. In this case, we won't retry this request since this request is already done and this is not a safe method to retry.
I think we should not propagate the error code to upper layer, since the request is done. We could just ignore this error.

Comment 7

[Kershaw Chang [:kershaw]]

Attachment: Bug 1940663 - When tranaction is done, treat NS_ERROR_NET_RESET as NS_OK, r=#necko

Comment 8

[Pulsebot]

Pushed by [e-mail]:
https://hg.mozilla.org/integration/autoland/rev/5ee377df59e8
When tranaction is done, treat NS_ERROR_NET_RESET as NS_OK, r=necko-reviewers,valentin

Comment 9

[Cristian Tuns]

https://hg.mozilla.org/mozilla-central/rev/5ee377df59e8

Comment 10

[mspclaims]

Thank you!