I suggest simply adding a giant banner[1] warning users and compiling a robots.txt <https://developers.google.com/search/docs/crawling-indexing/robots/robots_txt> for SSO.
[1] I believe we can do this by simply editing a couple of CSS files, instead of modifying every single HTML. On Mon, Mar 4, 2024 at 10:59 PM Piotr P. Karwasz <piotr.karw...@gmail.com> wrote: > Hi Ralph, > > On Mon, 4 Mar 2024 at 20:53, Ralph Goers <ralph.go...@dslextreme.com> > wrote: > > > On Mar 4, 2024, at 6:24 AM, Piotr P. Karwasz <piotr.karw...@gmail.com> > wrote: > > > > > > There is a further simplification possible: since Oracle's extended > > > support for Java 7 has expired in July 2022, shouldn't we also > > > redirect the `2.3.x` and `2.12.x` websites to `2.x`? > > > > Why would we do that? I mean we don’t officially support Java 6 or 7 yet > we did create patches for them for Log4Shell. While I hope they never need > to be updated again I don’t think it hurts anything to leave the doc alone. > > A simple Google search for `ThreadContextMap`: > > https://www.google.com/search?q=ThreadContextMap > > returns as first result a link to the javadoc of Log4j 2.4. While this > is currently redirected permanently to `/log4j/2.12.x/`, it is still > not the most recent documentation of the interface. How is the user > supposed to know, that this is the documentation for an old version? > > We could at least add a banner to all the pages with a link to the > most recent documentation and exclude the `/log4j/2.3.x/` and > `/log4j/2.12.x/` websites from being indexed by search engines. > > Piotr >
