Closed
Bug 193532
Opened 22 years ago
Closed 22 years ago
Conn: simulate a slow link for testing page load times (limiting used bandwidth, throttling downloads)
Categories
(Core :: Networking, enhancement)
Core
Networking
Tracking
()
VERIFIED
WONTFIX
People
(Reporter: vdvo, Assigned: dougt)
Details
User-Agent: Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.3b) Gecko/20030210
Build Identifier: Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.3b) Gecko/20030210
I'd like to have a way to simulate a slow link by:
1) setting a limit on the used bandwidth
2) simulating latency.
This would be priceless when creating web pages and optimizing them for download
speed. When this is activated, this should apply to all URL's, including local
(file://). Also, the cache should perhaps be disabled in this mode.
This is NOT a dupe of bug 101711 as that one deals with downloading individual
files. It could be blocked by it, though.
Reproducible: Always
Steps to Reproduce:
Comment 1•22 years ago
|
||
Wouldn't it be better to leave this out of the already-complicated browser
networking code and just run a proxy server to do it? (this won't apply to
file://, but I'd really rather not slow down our file:// stuff with unnecessary
checks for whether this option is activated, since that gets hit a lot during
startup....)
Comment 2•22 years ago
|
||
agreed.. marking WONTFIX.
Status: UNCONFIRMED → RESOLVED
Closed: 22 years ago
Resolution: --- → WONTFIX
VERIFIED:
People who want to test this really need a rate-limitng router and/or dialup
server. There are many aspects of a slow link that would not be correctly
reproducible by having a rate-limiting feature in Necko.
Status: RESOLVED → VERIFIED
Summary: rfe: a way to simulate a slow link for testing page load times (limiting used bandwidth, throttling downloads) → Conn: simulate a slow link for testing page load times (limiting used bandwidth, throttling downloads)
You need to log in
before you can comment on or make changes to this bug.
Description
•