NW 66 - URLDownload Error Codes (24-April-2000)
Q: When calling the URLDownload
function in the URL Access Manager, I occasionally see result
codes that are not documented for this function. What do
these errors mean?
A: Here are the meanings of some additional result
codes that may be returned by URLDownload :
The first two are internal errors returned from the
SSL code used by URL Access.
- -10: The server requires 128-bit encryption, but the
client does not support it. (URL Access currently
provides 40-bit encryption only.)
- -15: The URL Access Manager does not have the
server's root certificate and thus cannot validate the
certificate received from the server. There is no mechanism
to add new root certificates to URL Access, so to work around
this limitation you will need to add a certificate to your
server that is known to URL Access.
For your reference, here are the root certificates contained in URL Access
Manager 2.0 which shipped with Mac OS 9.0:
Netscape test CA key
Verisign c1 pca g2 v2 key
Verisign c2 pca g2 v2 key
Verisign c3 pca g2 v2 key
Verisign c4 pca g2 v2 key
Verisign pca1ss v4 key
Verisign pca2ss v4 key
Verisign pca3ss v4 key
RSA secure server ca key
Thawte server premium key
Thawte Personal basic key
Thawte Personal free key
Thawte Personal premium key
Thawte server basic key
Trust Center C0 key
Trust Center C1 key
Trust Center C2 key
Trust Center C3 key
Trust Center C4 key
Trust Center Demo key
Trust Center Proven Server key
Trust Center Server key
The third is an internal TCP-level error:
- -23008: A connection used by URL Access no longer
exists. This is usually a benign condition since HTTP
provides for recovery if a connection is unexpectedly
closed.
Technical Q&A | Contents
Previous Question | Next Question
To contact us, please use the Contact
Us page.
|