Re: Apache-SSL "suppresses" inlime images?
Well, I'm not sure but again I have a question. What about things like
MinSpareServers, MaxSpareServers and KeepAlive? If there aren't enough
spare children running, then some requests may drop. Subsequent requests
find some graphics in the local cache and then request the ones that
didn't make it last time. Dunno, but take a look.
Ernest Johanson
Web Systems Administrator
Fuller Theological Seminary
On Fri, 20 Aug 1999, Ralf G. R. Bergs wrote:
> Date: Fri, 20 Aug 1999 22:12:49 +0200
> From: Ralf G. R. Bergs <rabe@RWTH-Aachen.DE>
> To: Ernest Johanson <ejohan@fuller.edu>,
"paulwade@greenbush.com" <paulwade@greenbush.com>
> Subject: Re: Apache-SSL "suppresses" inlime images?
>
> Hi Guys,
>
> strange, I must have somehow missed your messages on the mailing list...
>
> Anyway, here we go...
>
> On Fri, 20 Aug 1999 15:42:52 -0400 (EDT), paulwade@greenbush.com wrote:
>
> >> Don't know that I have an answer, but a question. How are standard port
> 80
> >> connections being made to Apache-SSL? By default it runs on port 443.
>
> Here's a few excerpts from my httpd.conf:
>
> =============== 8x ================
> Port 80
> BindAddress *
> ServerName <my externally visible hostname>
> UseCanonicalName off
> # ----------------------------SSL----------------------------------
> Listen 80
> Listen 443
> SSLDisable
>
> <VirtualHost "my externally visible hostname":443>
> SSLEnable
> </VirtualHost>
>
> <VirtualHost "internal hostname":443>
> SSLEnable
> </VirtualHost>
> =============== 8x ================
>
> Do you see anything that looks fishy? Or anything that's missing?
>
>
> >> The only thing I've seen like this is when a page accessed via https
> >> contains full URLs ("http://whatever";). The ssl server views those
> >> elements as insecure and refuses to load them. Not the same as your
> >> situation, but perhaps a clue.
>
> I don't think this is helpful in my situation. There aren't any absolute
> URLs in my web pages. And remember that pressing reload a couple of times
> finally gives me all the inline graphics I expect.
>
> >It sounds like the answer because if you don't listen on port 80 you don't
> >log anything. The way I always do it is to use VirtualHost directives and
> >specify the port:
> >
> ><VirtualHost ssl.foo.com:443>
> ><VirtualHost www.foo.com:80>
>
> As you see above this is exactly how I'm doing it.
>
> Ok, any other ideas?
>
> Thanks for your help so far.
>
> Ralf
>
>
> --
> Sign the EU petition against SPAM: L I N U X .~.
> http://www.politik-digital.de/spam/ The Choice /V\
> of a GNU /( )\
> Generation ^^-^^
>
>
>
Reply to: