Closed Bug 1678843 Opened 4 years ago Closed 4 years ago

firefox https-only connection timeout too low

Categories

(Core :: DOM: Security, defect)

Product:
Core
Component:
DOM: Security
Version:
Firefox 83
Type:
defect

Tracking

()

Status:
RESOLVED INCOMPLETE

People

(Reporter: c7420, Unassigned)

References

(Blocks 1 open bug)

Details

User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:83.0) Gecko/20100101 Firefox/83.0

Steps to reproduce:

Access a http site (note: not https) and setting up an exception for the firefox native new https-only mode. Turning off the https-only mode resolves the issue and restores expected timeout length.

Actual results:

The website times out too soon (~2-3 seconds).

Expected results:

The timeout in https-only mode should be just as long as in non https-only mode.

Bugbug thinks this bug should belong to this component, but please revert this change in case of error.

Component: Untriaged → Networking: HTTP
Product: Firefox → Core
Component: Networking: HTTP → DOM: Security

Thanks for reporting this bug!
This is strange behavior because we don't instantly time out after 3 seconds but send a background HTTP request after 3 seconds. Only if this one comes back and there was no response from the HTTPS request, then we call it a timeout.

Do you have a website where I can try to reproduce this?

In the meantime, going to about:config and setting dom.security.https_only_mode_send_http_background_request to false should fix this for you for now :)

Blocks: https-only-mode
Flags: needinfo?(c7420)

Closing as INCOMPLETE due to lack of interaction.

Status: UNCONFIRMED → RESOLVED
Closed: 4 years ago
Flags: needinfo?(c7420)
Resolution: --- → INCOMPLETE

I experienced this problem with a private site that took long to respond when it ran too many database queries. Skipping the queries made Firefox receive a response in time and display the website.

On another occasion when I was developing a website and debugging a web view, I inserted a breakpoint and started a debugger. This normally makes Firefox wait for the debug session to finish and then proceed with processing the response. When HTTPS-everywhere is enabled, Firefox returns with a timeout 3 seconds after the debugger was invoked.

I'm not sure if this is intended behaviour or not.

Flags: needinfo?(ckerschb)

Interesting. So how does this private site respond to HTTP requests? Does it send a redirect to HTTPS?

The issues you're describing with the debugger probably warrant a new bug. I can also do that, but it'd be great if you could give me a description of how to reproduce the debugger problem.

Flags: needinfo?(ckerschb) → needinfo?(c7420)

OP here, I can no longer reproduce this. I am sorry for wasting everyones time.

Flags: needinfo?(c7420)
You need to log in before you can comment on or make changes to this bug.