Re: lilypond.org now serving HTTPS

[Han-Wen Nienhuys]

I don't quite get how the automatic generation worked, but after I
removed out-website/ and reran the make, it worked. The english
version is now considered secure.

The translated pages still have mixed mode data. Is it OK to edit
these directly in the source tree, or will that upset our translation
infrastructure?

On Thu, Feb 20, 2020 at 11:30 PM Han-Wen Nienhuys <address@hidden> wrote:
>
> I think the automatic update of lilypond.org has stopped working. Let
> me look into it.
>
> On Thu, Feb 20, 2020 at 10:03 PM Joram Noeck <address@hidden> wrote:
> >
> > > My browser complains about mixed content, i.e. http-linked media on the
> > > page.
> > >
> > > Urs
> >
> > Here (Firefox 73), the only warning is about the "Valid HTML 4.01" image
> > in the page footer. All other images (on the pages I looked at) have
> > relative src attributes and are served directly from lilypond.org via https.
> >
> > Joram
> >
> >
> >
> > PS: Btw, the only other warning I get is about -moz-border-radius which
> > was renamed to border-radius (without vendor prefix) in 2011 if I am not
> > mistaken.  I also see commits that changed this in 2015¹, but perhaps
> > too late for the 2.18 website? Or I don't why the latest css is not served.
> >
> >
> > ¹:
> > https://github.com/lilypond/lilypond/commit/a6f369ae2efe399ef9644a702d98187e93129a87
>
>
>
> --
> Han-Wen Nienhuys - address@hidden - http://www.xs4all.nl/~hanwen



-- 
Han-Wen Nienhuys - address@hidden - http://www.xs4all.nl/~hanwen