Open
Bug 196076
Opened 22 years ago
Updated 2 years ago
add support for more DNS error codes
Categories
(NSPR :: NSPR, defect)
NSPR
NSPR
Tracking
(Not tracked)
NEW
People
(Reporter: benc, Unassigned)
References
(Blocks 2 open bugs)
Details
As I understand it, NSPR only has only one error code right now (Bug 164715 #7)
Ideally, NSPR would add support for a couple more error codes:
> gethostbyname() has four error codes:
>
> #define HOST_NOT_FOUND 1 /* Authoritive Answer Host not found */
> #define TRY_AGAIN 2 /* Non-Authoritive Host not found, or
> SERVERFAIL */
> #define NO_RECOVERY 3 /* Non recoverable errors, FORMERR, REFUSED,
> NOTIMP */
> #define NO_DATA 4 /* Valid name, no data record of requested
> type */
This might need platform specific attention.
Right now, we can't do things like error saying that we could not contact the
DNS server. This is a distinct problem from requesting a hostname that is not in
DNS (for example, the root cause if often connectivity problems).
Updated•18 years ago
|
QA Contact: wtchang → nspr
Comment 1•17 years ago
|
||
why version=other?
Updated•2 years ago
|
Severity: normal → S3
Comment 2•2 years ago
|
||
The bug assignee is inactive on Bugzilla, so the assignee is being reset.
Assignee: wtc → nobody
You need to log in
before you can comment on or make changes to this bug.
Description
•