On Wed, Apr 2, 2008 at 3:39 PM, Bill Moseley <<a href="mailto:moseley@hank.org">moseley@hank.org</a>> wrote:<br><div class="gmail_quote"><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div class="Ih2E3d">On Wed, Apr 02, 2008 at 03:14:09PM -0700, Ask Bjørn Hansen wrote:<br>
><br>
> On Apr 2, 2008, at 15:06, Bill Moseley wrote:<br>
><br>
> >That's where directory indexes work fine under SSL but fetching files<br>
> >returns the SSL error.<br>
><br>
><br>
> Eeek - my apologies, I'm obviously half asleep at the wheel here. I<br>
> don't use the file serving mode in perlbal, sorry!<br>
<br>
</div>No problem -- hidden config setting.<br>
<br>
Should I assume that SSL and the web_server role do not work together<br>
and move on? I have an Apache running behind perlbal that can serve<br>
static content.</blockquote><div><br>That is correct: SSL only works for proxying, not for serving.<br><br>The problem is the web_server role proceeds to do a sendfile() right to the raw socket, sending unencrypted data right onto the already-SSL-connected socket, corrupting the stream.<br>
<br>Somebody should fix that. :-) At least make it a config error to try that.<br><br></div></div>