Frank, Nelson, just in case it's useful...
I recall that GlobalSign recently refreshed their GlobalSign Root CA:
https://bugzilla.mozilla.org/show_bug.cgi?id=406794
When the new GlobalSign Root CA certificate (which expires in 2028) was added
to NSS, the old certificate (which expires in 2014)
Yes, the server sent me all the data and then closed the connection.
And NSPR should have received all the data and stored in its buffers.
The returned the data to the client application through PR_Read.
But this is not happening because PR_Read returns 0, even though it should
have more data in
Hi Nelson,
Yes, I did some more tests.
The server sends the data and then closes the connection(becuase we use HTTP
Connection:close and not Keep-Alive).
But shouldnt PR_Read return the entire data and then only return 0(becuase
the connection is closed).
How can it return 0, before all the
(Sorry for the apparent tardiness of this reply. I wrote it the day that
I read Frank's message, and thought I sent it, but evidently did not send
it until today.)
Frank Hecker wrote, On 2009-05-22 07:24 PDT:
So, just to clarify: I *think* you're proposing that we do the following
in cases
Rob Stradling wrote, On 2009-05-27 01:35:
Frank, Nelson, just in case it's useful...
I recall that GlobalSign recently refreshed their GlobalSign Root CA:
https://bugzilla.mozilla.org/show_bug.cgi?id=406794
When the new GlobalSign Root CA certificate (which expires in 2028) was added
to
Rolf Lindemann wrote, On 2009-05-24 09:52 PDT:
Do you know which version of Thunderbird will get the NSS version containing
the new root certificates?
No. I would hope that the upcoming Thunderbird 3 release would include
them, but I cannot say with any certainty that it will. This might be
Vinu wrote, on 2009-05-27 15:26 PDT:
The server sends the data and then closes the connection(becuase we use HTTP
Connection:close and not Keep-Alive).
But shouldnt PR_Read return the entire data and then only return 0(becuase
the connection is closed).
How can it return 0, before all the
I've been looking at the problem of different libraries/different
clients each with their own private key/cert db in a single process (for
example, the Thunderbird ldap/nss_ldap problem). In this case, the user
may want nss_ldap to keep its certs and keys (including ca certs)
separate from
8 matches
Mail list logo
