Closed Bug 867872 Opened 7 years ago Closed 4 years ago

implement standardizable errors for mozTCPSocket (and XHR), consider proposed TCPError implementation

Categories

(Core :: Networking, defect)

x86_64
Linux
defect
Not set

Tracking

()

RESOLVED WONTFIX

People

(Reporter: asuth, Unassigned)

References

Details

Attachments

(1 file)

For bug 861196 implementing improved error reporting for security (and network) errors encountered by mozTCPSocket, I wanted to implement a custom error class, TCPError.  This proved to:
- be very hard to do on mozilla-b2g18 (the target / driving impetus)
- be something you don't want to rush; as bsmith pointed out, it's hard to design good errors that can be standardized as ASAP.

The general idea I wanted was to have an error implementation that had an attribute that indicated the type of error in broad strokes so that the most specific set of errors could change but application logic/application UI would not depend on them in a brittle fashion, such as using a switch or (less brittle but still bad) a RegExp.

It appears there is potentially other information that might want to be relayed, per bsmith, such as things related to strict transport security.

I am enclosing the TCPError.webidl which mainly documents the existing error codes I have mapped in TCPSocket.js.
Depends on: 870856
subsumed by different spec
Status: NEW → RESOLVED
Closed: 4 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.