On 21/07/17 09:47, Tony Marston wrote: > Why on earth should you need to use HTTPS for a website that does not > deal with personal information? Nothing on that website can possibly be > classed as "sensitive" so what would be the point?
That applies to many of the websites I support yet the likes of Google and Bing now 'downrate' sites that don't have https and browsers complain about 'insecure' sites. Add the problems created when you add a private https area to a 'public' domain name and things get even messier. That some people even here insist that HTTP should be killed off seems not to have been thought through at all? On the website front, the problem I see is that while the MANUAL is a static site, adding things like the wiki, bug system, pecl/pear management, and other dynamic areas and allowing a decent CLEAN cross content search is what I see as being needed. Add managed translations then while a single static english copy of the main stuff is easy to distribute, and dynamic set of content WOULD be easier going forward. Except there would never be any agreement on how THAT would be managed and on which database engine :( -- Lester Caine - G8HFL ----------------------------- Contact - http://lsces.co.uk/wiki/?page=contact L.S.Caine Electronic Services - http://lsces.co.uk EnquirySolve - http://enquirysolve.com/ Model Engineers Digital Workshop - http://medw.co.uk Rainbow Digital Media - http://rainbowdigitalmedia.co.uk -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
