User: clokkevi

Why did SAME *.crl needed to be dl'd MANY times?

On: Verisign Certificate Expiration Causes Multiple Problems

First - thanks for letting me know what happened!

For me, the trouble was NAV intercepting all my right-clicks.

But the thing I don't understand, is:
I packet-monitored what happened, so I saw that my PC connected to http://64.94.110.11/

This was the "conversation":

My PC:
GET /Class3SoftwarePublishers.crl HTTP/1.1
Accept: */*
User-Agent: CryptRetrieveObjectByUrl::InetSchemeProvider
Host : crl.verisign.com
Connection: Keep-Alive
Cache-Control: no-cache
Cookie: v1st=3E9B2224FB5AAB53

VeriSign CRL:
HTTP/1.1 200 OK
Date: Thu, 08 Jan 2004 23:23:05 GMT
Server: Apache
Last-Modified: Thu, 08 Jan 2004 16:18:40 GMT
ETag: "ac04-192-3ffd82e0"
Accept-Ranges: bytes
Content-Length: 402
Connection: close
Content-Type: text/plain

0Z0o0 *H/ 0E10U VeriSign, Inc.10UVeriSign Trust Network1F0DU=www.verisign.com/repository/RPA Incorp. by Ref.,LIAB.LTD(c)981D0BU;VeriSign Class 3 CA - Commercial Content/Software Publisher 040106000000Z 040409235959Z0 *H/ eSY}u"Wfb`C($Vu;m-v9ufO)uOwZ'A'o?(UI/|

___________________________________________

I right-clicked once more, and checked also *that* "conversation" - and it was the same, apart from the timestamps.

So - apparently that CRL server was not *completly* DOS'ed - altough it tokk 5-10 seconds before the reply came.

Why did my PC need to download that SAME *.crl - Class3SoftwarePublishers.crl - so MANY times???

I also - for fun - downloaded all the 51 *.crl's on that server, *manually*, to look at them. (Until yesterday, I had no idea what a *.crl was)
And I did get all those 2.57MB downloaded, although it took some minutes. So, I'm 100% sure that CRL server was not *completly* DOS'ed.

Or have I misunderstood it all! Was the http://64.94.110.11/ site maybe the VeriSign "fix"? If so - then I apologize for being so stupid. But still, my 1st question remains:

Why the numerous downloads of the SAME file?

With regards,

Clokkevi.