The problem is: SSL is *NOT* usable for virtual hosting. You need an separate socket for each SSL vhost, so you'll probably prefere several independent httpd's - maybe then stripped down w/o any vhost support.You're right - SSL is not usable for name-based vhosts. However it should be fine for normal vhosts. Are you suggesting I use a separate httpd for every SSL host I have? That's a waste of resources, and horribly inefficient. Can metuxmpm deal with non name-based SSL vhosts?
As you have correctly surmised we'd be doing all this in kernel space. This isn't something Apache needs to support natively, I'm merely putting forward a consideration from my POV.Aehm, what exactly do you want to do ?
Measure users's consumed traffic ? (-> logfile ?) Measure users's consumed bandwidth ? (eh, does this make sense at all? ) Limit user's bandwidth ? (very complicated w/o proper kernel support)
PS. Not subscribed to the mailing list and checking this via gmane. So, copying replies to me is a good idea if you want a response!
Thanks,
Nick Maynard [EMAIL PROTECTED]
