This is an automated email from the ASF dual-hosted git repository.
pkarwasz pushed a commit to branch asf-site
in repository https://gitbox.apache.org/repos/asf/logging-log4j-site.git
The following commit(s) were added to refs/heads/asf-site by this push:
new bf20e759d4 More broken links
bf20e759d4 is described below
commit bf20e759d4186b5d61963783b3eabf6e827af79c
Author: Piotr P. Karwasz <[email protected]>
AuthorDate: Fri Apr 19 18:17:59 2024 +0200
More broken links
---
1.x/index.html | 20 ++++++++++----------
1 file changed, 10 insertions(+), 10 deletions(-)
diff --git a/1.x/index.html b/1.x/index.html
index 0316c78849..b782f930d4 100644
--- a/1.x/index.html
+++ b/1.x/index.html
@@ -48,7 +48,7 @@
<div class="xleft">
<span id="publishDate">Last Published: 2012-05-13</span>
| <span id="projectVersion">Version: 1.2.17</span>
- | <a
href="http://www.apache.org/"; class="externalLink" title="Apache">Apache</a>
+ | <a
href="https://apache.org/"; class="externalLink" title="Apache">Apache</a>
>
<a href="../../" title="Logging
Services">Logging Services</a>
>
@@ -124,19 +124,19 @@
<h5>Apache</h5>
<ul>
<li class="none">
- <a href="http://www.apache.org"; class="externalLink"
title="Home">Home</a>
+ <a href="https://apache.org"; class="externalLink"
title="Home">Home</a>
</li>
<li class="none">
- <a href="http://www.apache.org/licenses";
class="externalLink" title="License">License</a>
+ <a href="https://apache.org/licenses/";
class="externalLink" title="License">License</a>
</li>
<li class="none">
- <a
href="http://www.apache.org/foundation/sponsorship.html"; class="externalLink"
title="Sponsorship">Sponsorship</a>
+ <a href="https://apache.org/foundation/sponsorship";
class="externalLink" title="Sponsorship">Sponsorship</a>
</li>
<li class="none">
- <a
href="http://www.apache.org/foundation/thanks.html"; class="externalLink"
title="Thanks">Thanks</a>
+ <a href="https://apache.org/foundation/sponsors";
class="externalLink" title="Thanks">Thanks</a>
</li>
<li class="none">
- <a href="http://www.apache.org/security/";
class="externalLink" title="Security">Security</a>
+ <a href="https://apache.org/security/";
class="externalLink" title="Security">Security</a>
</li>
<li class="none">
<a href="http://www.apachecon.com";
class="externalLink" title="Conferences">Conferences</a>
@@ -151,7 +151,7 @@
</div>
<div id="bodyColumn">
<div id="contentBox">
- <!-- Licensed to the Apache Software Foundation (ASF) under one or
more --><!-- contributor license agreements. See the NOTICE file distributed
with --><!-- this work for additional information regarding copyright
ownership. --><!-- The ASF licenses this file to You under the Apache License,
Version 2.0 --><!-- (the "License"); you may not use this file except in
compliance with --><!-- the License. You may obtain a copy of the License at
--><!-- --><!-- http://www.apache.org/ [...]
+ <!-- Licensed to the Apache Software Foundation (ASF) under one or
more --><!-- contributor license agreements. See the NOTICE file distributed
with --><!-- this work for additional information regarding copyright
ownership. --><!-- The ASF licenses this file to You under the Apache License,
Version 2.0 --><!-- (the "License"); you may not use this file except in
compliance with --><!-- the License. You may obtain a copy of the License at
--><!-- --><!-- https://apache.org/lic [...]
<div class="section">
<h2>End of Life</h2><p>On August 5, 2015 the Logging Services
Project Management Committee announced that Log4j 1.x had reached end of life.
For complete text of the announcement please see the <a
href="http://blogs.apache.org/foundation/entry/apache_logging_services_project_announces";>Apache
Blog</a>. Users of Log4j 1 are recommended to upgrade to <a
class="externalLink" href="/log4j/2.x/">Apache Log4j 2</a>.</p>
<h2>Security Vulnerabilities</h2>
@@ -167,7 +167,7 @@
<p>The version detection algorithm changed in Java 9 which
causes the MDC not to work properly. See <a
href="https://blogs.apache.org/logging/entry/moving_on_to_log4j_2";>Log4j 1.2 is
broken on Java 9</a> for details.</p>
<h2>Other issues of note</h2>
<p>Log4j 1 doesn't restrict DTD entities in log4j.xml. Users
should be careful to ensure any entities specified are correct and secure.</p>
- <h2>Apache log4j™ 1.2<a
name="Apache_log4j_1.2"></a></h2><p>Welcome to Apache log4j, a logging library
for Java. Apache log4j is an Apache Software Foundation Project and developed
by a dedicated team of Committers of the Apache Software Foundation. For more
info, please see <a class="externalLink" href="http://www.apache.org";>The
Apache Software Foundation</a>. Apache log4j is also part of a project which is
known as <a class="externalLink" href="http://logging.apac [...]
+ <h2>Apache log4j™ 1.2<a
name="Apache_log4j_1.2"></a></h2><p>Welcome to Apache log4j, a logging library
for Java. Apache log4j is an Apache Software Foundation Project and developed
by a dedicated team of Committers of the Apache Software Foundation. For more
info, please see <a class="externalLink" href="https://apache.org";>The Apache
Software Foundation</a>. Apache log4j is also part of a project which is known
as <a class="externalLink" href="http://logging.apache. [...]
<div class="section"><h3>Why logging?<a
name="Why_logging"></a></h3><p>Inserting log statements into your code is a
low-tech method for debugging it. It may also be the only way because debuggers
are not always available or applicable. This is often the case for distributed
applications.</p><p>On the other hand, some people argue that log statements
pollute source code and decrease legibility. (We believe that the contrary is
true). In the Java language where a preprocessor [...]
<div class="section"><h3>Why log4j?<a
name="Why_log4j"></a></h3><p>With log4j it is possible to enable logging at
runtime without modifying the application binary. The log4j package is designed
so that these statements can remain in shipped code without incurring a heavy
performance cost. Logging behavior can be controlled by editing a configuration
file, without touching the application binary.</p><p>Logging equips the
developer with detailed context for application failur [...]
<div class="section"><h3>Performance<a
name="Performance"></a></h3><p>On an AMD Duron clocked at 800Mhz running JDK
1.3.1, it costs about 5 nanoseconds to determine if a logging statement should
be logged or not. Actual logging is also quite fast, ranging from 21
microseconds using the SimpleLayout, 37 microseconds using the TTCCLayout. The
performance of the PatternLayout is almost as good as the dedicated layouts,
except that it is much more flexible.</p></div>
@@ -179,10 +179,10 @@
</div>
<div id="footer">
<div class="xleft">Copyright © 1999-2012
- <a href="http://www.apache.org";>Apache Software
Foundation</a>.
+ <a href="https://apache.org";>Apache Software
Foundation</a>.
- Licensed under the <a
href="http://www.apache.org/licenses/LICENSE-2.0";>Apache Software License,
Version 2.0</a>.</div>
+ Licensed under the <a
href="https://apache.org/licenses/LICENSE-2.0";>Apache Software License, Version
2.0</a>.</div>
<div class="xleft">Apache Extras Companion for Apache log4j, Apache
log4j, Apache, the Apache feather logo,
the Apache Logging Services project logo, the log4j logo, and the Built by
Maven logo are trademarks of The Apache Software Foundation. Oracle and Java
are registered trademarks of Oracle and/or its affiliates. Other names may be
trademarks of their respective owners.</div>
<div class="clear">
