Open Bug 1575856 Opened 5 years ago Updated 2 years ago

Improve TRR timeout logic to start the timer only after we have sent the request

Categories

(Core :: Networking: DNS, task, P3)

Product:
Core
Component:
Networking: DNS
Type:
task

Tracking

()

People

(Reporter: mayhemer, Unassigned)

References

Details

(Whiteboard: [necko-triaged])

Right now the timeout includes both proxy connection establishment + e2e connection establishment. That's not right because on slower nets this can timeout for no good reason.

We should start the timer when we get NS_NET_STATUS_WAITING_FOR state.

Also consider increasing the 1500ms to something slightly bigger.

Priority: -- → P3
Whiteboard: [necko-triaged]

Mass-removing myself from cc; search for 12b9dfe4-ece3-40dc-8d23-60e179f64ac1 or any reasonable part thereof, to mass-delete these notifications (and sorry!)

Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.