[hunchentoot-devel] Two questions

[Nicolas Neuss]

"Andrea Chiumenti" <kiuma72 at gmail.com> writes:

>     > ProxyPass /hunchentoot/ http://127.0.0.1:8005/
>     > ProxyPassReverse /hunchentoot/ http://127.0.0.1:8005/
>
> have you tried something like
> ProxyPass /hunchentoot/ggg http://127.0.0.1:8005/ggg
> ProxyPassReverse /hunchentoot/ggg http://127.0.0.1:8005/ggg

No, because at the moment, I do not have subdirectories. 

> On Fri, Mar 14, 2008 at 6:15 PM, Edi Weitz wrote:
>
>     > 2. Is it possible to change the above setup such that it forwards
>     > secure connections?
>    
>     Sure.  Put the directives into a virtual server which serves https
>     connections.  IIUC that should be all you need.

I have tried now in httpd.conf the following:

<VirtualHost localhost:443>
ServerName localhost
SSLEngine on
SSLCertificateFile /home/neuss/CL-HOME/courses/server.cert
SSLCertificateKeyFile /home/neuss/CL-HOME/courses/server.key
ProxyPass /hunchentoot/ https://127.0.0.1:8005/
ProxyPassReverse /hunchentoot/ https://127.0.0.1:8005/
</VirtualHost>

However, although https://127.0.0.1:8005/ works, when I access it with
https://localhost/hunchentoot/, I see the following error in the log file:

[2008-03-15 19:23:16 [ERROR]] Error while processing connection: The
TLS/SSL connection on handle #.(SB-SYS:INT-SAP #X080FFD68) has been
closed. (return code:  5)SSL error queue: 

Does anyone see what I'm doing wrong here?

Thank you,
Nicolas

P.S.: Here is the longer backtrace:

  0: ((LAMBDA (SWANK-BACKEND::DEBUGGER-LOOP-FN))
      #<FUNCTION (LAMBDA #) {A8D0DDD}>)
  1: (SWANK::DEBUG-IN-EMACS #<CL+SSL::SSL-ERROR-ZERO-RETURN {B0E36D1}>)
  2: ((LAMBDA (SWANK-BACKEND::HOOK SWANK-BACKEND::FUN))
      #<FUNCTION SWANK:SWANK-DEBUGGER-HOOK>
      #<CLOSURE (LAMBDA #) {B0E3905}>)
  3: (SWANK::CALL-WITH-REDIRECTED-IO
      #<SWANK::CONNECTION {ADC8DC9}>
      #<CLOSURE (LAMBDA #) {B0E3915}>)
  4: (SWANK::CALL-WITH-CONNECTION
      #<SWANK::CONNECTION {ADC8DC9}>
      #<CLOSURE (LAMBDA #) {B0E3905}>)
  5: (INVOKE-DEBUGGER #<CL+SSL::SSL-ERROR-ZERO-RETURN {B0E36D1}>)
  6: (INVOKE-DEBUGGER #<CL+SSL::SSL-ERROR-ZERO-RETURN {B0E36D1}>)
  7: ((SB-PCL::FAST-METHOD HUNCHENTOOT:MAYBE-INVOKE-DEBUGGER (T))
      #<unavailable argument>
      #<unavailable argument>
      #<CL+SSL::SSL-ERROR-ZERO-RETURN {B0E36D1}>)
  8: ((LAMBDA
          (SB-PCL::.PV-CELL. SB-PCL::.NEXT-METHOD-CALL. SB-PCL::.ARG0.))
      #<unavailable argument>
      #<unavailable argument>
      #<CL+SSL::SSL-ERROR-ZERO-RETURN {B0E36D1}>)
  9: (SIGNAL #<CL+SSL::SSL-ERROR-ZERO-RETURN {B0E36D1}>)
 10: (ERROR CL+SSL::SSL-ERROR-ZERO-RETURN)
 11: (CL+SSL::SSL-SIGNAL-ERROR
      #.(SB-SYS:INT-SAP #X0810FC90)
      #<FUNCTION CL+SSL::SSL-ACCEPT>
      5
      0)
 12: (CL+SSL::SSL-SIGNAL-ERROR
      #.(SB-SYS:INT-SAP #X0810FC90)
      #<FUNCTION CL+SSL::SSL-ACCEPT>
      5
      0)
 13: (CL+SSL:MAKE-SSL-SERVER-STREAM #<unavailable lambda list>)
 14: (HUNCHENTOOT::PROCESS-CONNECTION
      #<HUNCHENTOOT::SERVER {B74C2F1}>
      #<SB-BSD-SOCKETS:INET-SOCKET descriptor 11 {AE8D8A9}>)
 15: ((LAMBDA ()))