I'm awake.

Just woke up from a stuuuupid dream. I don't know if the dumbness of the dream was caused by my illness, or if the fact that I can tell it was real dumb means my illness is on the wane. Anyway, I feel somewhat better now, and will drink coffee and get some breakfast, and see how that sits with me.

Today's Humorous Interlude from TwoLumps

( Comic Funnies! )

Illness update.

Well, the coffee and breaky went down okay. I still have a nagging headache, but the nausea hasn't returned, and I think I can think again.

Maybe a hot shower will bring me the rest of the way back to life.

Ig Nobel Prizes for 2004

See the whole list here. My favorites this year are:

• How to be invisible while wearing a Gorilla Suit.
• The patenting of the comb-over.
• The connection between country-music and suicide.

https:\Grump.

I spent the day looking into the whole virtual-name-hosting of https. What everyone has been saying is indeed true. It can't be done. There simply isn't a way permitted by the protocol to define a multiplex https port.

The reason for this is that the first thing that happens during the protocol is that the client asks 'Who are you?', and the server must respond with a certificate that contains its domain address. Since a multiplex port has no way of determining which domain its being asked to respond as, there's nothing it can reply that is safe.

So, it looks like my server is only going to get ONE https domain for now. The current version of http+tls, (which replaces https) solves that problem neatly, but no one has bothered to implement it yet.