On Thu, Feb 19, 2015 at 6:01 PM, jan i <j...@apache.org> wrote:

> On Thursday, February 19, 2015, Keith N. McKenna <
> keith.mcke...@comcast.net>
> wrote:
>
> > jan i wrote:
> > > On 19 February 2015 at 14:14, Simon Phipps <si...@webmink.com
> > <javascript:;>> wrote:
> > >
> > >> On Thu, Feb 19, 2015 at 6:26 AM, jan i <j...@apache.org
> <javascript:;>>
> > wrote:
> > >>>
> > >>> On Thursday, February 19, 2015, Dennis E. Hamilton <
> > >> dennis.hamil...@acm.org <javascript:;>>
> > >>> wrote:
> > >>>
> > >>>>        "The connection to this web site is not fully secure
> > >>>>        because it contains unencrypted elements (such as
> > >>>>        images)."
> > >>
> > >>
> > >> Perhaps the line:
> > >>    <img src="http://www.openoffice.org/images/2014-eu-234x60.png";
> > >> alt="Logo
> > >> ApacheCon Europe 2014" />
> > >>
> > >
> > >
> > >>
> > >> is causing this?
> > >>
> > > A very  good idea...since this will cause a jump from HTTPS to HTTP. I
> > had
> > > however expected another error for this.
> > >
> > > Funny thing is, that I do not get an error on that page, even with my
> > > Certificate analyzer.
> > >
> > > rgds
> > > jan I.
> > >
> > >>
> > >> S.
> > >>
> > >
> > I get the following warning with SeaMonkey 2.32.1. You have requested a
> > page that is only partially encrypted and does not prevent eavesdropping.
>
>
> that is the error I expected due to the img src calling http and not https.


Is there someone with commit access who could change that IMG tag to use
https so Brenda & Keith can check if that's the problem?

S.

Reply via email to