Closed Bug 201121 Opened 22 years ago Closed 9 years ago

[meta] Error handling for URLs loaded via <SRC>

Categories

(Core :: Networking, defect)

defect
Not set
normal

Tracking

()

RESOLVED WORKSFORME

People

(Reporter: benc, Unassigned)

References

Details

I've noticed a variety of bugs that say that <SRC> acts weird when common networking errors occur. I haven't seen anything that describes how it should work, and I don't have time to gather up all the data right now, so I'm creating this as a placeholder meta bug, so I won't forget. The three main errors that should always be handled are: DNS hostname not found. Connection refused (server answers, but does not use the requested port number) Timeout while establishing connection. Additionally, there are questions of user+password auth, timeouts during transmission, and page not found (404) errors.
-> benc ...feel free to send it back if there is something that should be fixed ;-)
Assignee: darin → benc
I don't think QA should be assigned meta bugs just because we created them... This is why we want to have default owner placeholders. Proper ownership model, no useless bugmail for engineers.
Assignee: benc → new-network-bugs
found a couple items...
Depends on: 42158, 72109, 151450, 162168
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.