Open Bug 1739626 Opened 3 years ago Updated 3 years ago

Slow Page Loading in PeopleSoft (with DoH enabled)

Categories

(Core :: Networking, defect, P3)

Firefox 91
defect

Tracking

()

UNCONFIRMED

People

(Reporter: jkopp, Unassigned)

References

(Blocks 1 open bug)

Details

(Whiteboard: [necko-triaged])

User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:91.0) Gecko/20100101 Firefox/91.0

Steps to reproduce:

I attempted to login and access any pages in PeopleSoft from behind the firewall.

Actual results:

Login and pages will load but extremely slowly.

Expected results:

Login and pages should load within 1 second. The solution is to Disable DNS over HTTP. Firefox should disable this function especially on esr versions when accessing content on the same and/or corporate network. There should also be a box for adding exceptions. This is an important feature that needs some enhancement.

The Bugbug bot thinks this bug should belong to the 'Core::Networking' component, and is moving the bug to that component. Please revert this change in case you think the bot is wrong.

Component: Untriaged → Networking
Product: Firefox → Core
Summary: Slow Page Loading in PeopleSoft → Slow Page Loading in PeopleSoft (with DoH enabled)

(In reply to jkopp from comment #0)

User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:91.0) Gecko/20100101 Firefox/91.0

Login and pages should load within 1 second. The solution is to Disable DNS over HTTP. Firefox should disable this function especially on esr versions when accessing content on the same and/or corporate network. There should also be a box for adding exceptions. This is an important feature that needs some enhancement.

You can add an excluded domain by going into about:config and add your domains to network.trr.excluded-domains.

TRR also excludes all domains that are part of the DNS suffix list from being resolved with DoH.

I agree that UI for adding TRR exceptions would be nice.

Blocks: doh
Severity: -- → S3
Priority: -- → P3
Whiteboard: [necko-triaged]
You need to log in before you can comment on or make changes to this bug.