svn revision 152 breaks support for https proxy about shellinabox

[GoogleCodeExporter]

I'll take a look at it in the next couple of days. That definitely sounds like 
unintended behavior. In the meantime, if you remove the --disable-ssl switch, 
it'll 
probably start working again; but that's obviously not quite correct in your 
situation.

Original comment by [email protected] on 7 Aug 2009 at 4:44

• Changed state: Accepted

[GoogleCodeExporter]

You are using ShellInABox in a slightly less common configuration. Most users 
would 
need ShellInABox to do the redirection from http: to https: for them, even if 
they 
used a reverse proxy for the SSL encryption. And they would therefore not set 
the --
disable-ssl option. Your situation is different, and I can understand why you 
would 
set --disable-ssl, as all the tricky encryption bits are handled by your 
reverse 
proxy.

I now committed a change to revision 162 of ShellInABox that will continue 
using 
encrypted sessions, even if you set the --disable-ssl option. This should get 
you 
back to the state that you had before I broke things for you. Please let me 
know if 
you continue seeing any issues, as your configuration tests an interesting 
corner 
case, and you might find bugs that I hadn't thought of.

Original comment by [email protected] on 8 Aug 2009 at 10:13

• Changed state: Fixed

[GoogleCodeExporter]

Thank you, it's working again now.

Original comment by [email protected] on 9 Aug 2009 at 9:35