Yes, one port. Maybe that is where my own internal logic is breaking down. I was thinking about one instance of Apache handling both ssl and non-ssl connections, though it uses separate ports. -austin -- Austin Haas Pet Tomato, Inc. http://pettomato.com On Mon Jul 09 17:17 , Ralf Mattes wrote:
On Mon, 2007-07-09 at 11:06 -0400, Austin Haas wrote:
If I am running Hunchentoot standalone with ssl, should it be able to handle requests that are NOT using ssl as well? Currently, I am getting the following error if I send a request to "http" and not "https":
Just to get things clear: are you trying to do this on _one_ port (i.e. non-SSL connects on the same port as SSL)?
Cheers, RalfD
_______________________________________________ tbnl-devel site list tbnl-devel@common-lisp.net http://common-lisp.net/mailman/listinfo/tbnl-devel