Server geändert

2023-04-25 13:17:57 +02:00
parent f1b11efb5d
commit f93fa77db7
603 changed files with 2951 additions and 2951 deletions
--- a/htmlpurifier-4.10.0/docs/enduser-customize.html
+++ b/htmlpurifier-4.10.0/docs/enduser-customize.html
@ -1,7 +1,7 @@
 <?xml version="1.0" encoding="UTF-8"?>
 <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
-    "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en"><head>
+    "https://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="https://www.w3.org/1999/xhtml" xml:lang="en" lang="en"><head>
 <meta http-equiv="Content-Type" content="text/html; charset=UTF-8" />
 <meta name="description" content="Tutorial for customizing HTML Purifier's tag and attribute sets." />
 <link rel="stylesheet" type="text/css" href="style.css" />
@ -15,7 +15,7 @@

 <div id="filing">Filed under End-User</div>
 <div id="index">Return to the <a href="index.html">index</a>.</div>
-<div id="home"><a href="http://htmlpurifier.org/">HTML Purifier</a> End-User Documentation</div>
+<div id="home"><a href="https://htmlpurifier.org/">HTML Purifier</a> End-User Documentation</div>

 <p>
  HTML Purifier has this quirk where if you try to allow certain elements or
@ -44,7 +44,7 @@

 <p>
  All of the modules listed below are based off of the
-  <a href="http://www.w3.org/TR/2001/REC-xhtml-modularization-20010410/abstract_modules.html#sec_5.2.">modularization of
+  <a href="https://www.w3.org/TR/2001/REC-xhtml-modularization-20010410/abstract_modules.html#sec_5.2.">modularization of
  XHTML</a>, which, while technically for XHTML 1.1, is quite a useful
  resource.
 </p>
@ -76,7 +76,7 @@

 <p>
  As of HTMLPurifier 2.1.0, we have implemented the
-  <a href="http://www.w3.org/TR/2001/REC-ruby-20010531/">Ruby module</a>,
+  <a href="https://www.w3.org/TR/2001/REC-ruby-20010531/">Ruby module</a>,
  which defines a set of tags
  for publishing short annotations for text, used mostly in Japanese
  and Chinese school texts, but applicable for positioning any text (not
@ -86,7 +86,7 @@
 <h3>HTML 5</h3>

 <p>
-  <a href="http://www.whatwg.org/specs/web-apps/current-work/">HTML 5</a>
+  <a href="https://www.whatwg.org/specs/web-apps/current-work/">HTML 5</a>
  is a fork of HTML 4.01 by WHATWG, who believed that XHTML 2.0 was headed
  in the wrong direction.  It too is a working draft, and may change
  drastically before publication, but it should be noted that the
@ -354,10 +354,10 @@ $def = $config-&gt;getHTMLDefinition(true);

 <p>
  For a complete list, consult
-  <a href="http://repo.or.cz/w/htmlpurifier.git?a=blob;hb=HEAD;f=library/HTMLPurifier/AttrTypes.php"><code>library/HTMLPurifier/AttrTypes.php</code></a>;
+  <a href="https://repo.or.cz/w/htmlpurifier.git?a=blob;hb=HEAD;f=library/HTMLPurifier/AttrTypes.php"><code>library/HTMLPurifier/AttrTypes.php</code></a>;
  more information on attributes that accept parameters can be found on their
  respective includes in
-  <a href="http://repo.or.cz/w/htmlpurifier.git?a=tree;hb=HEAD;f=library/HTMLPurifier/AttrDef"><code>library/HTMLPurifier/AttrDef</code></a>.
+  <a href="https://repo.or.cz/w/htmlpurifier.git?a=tree;hb=HEAD;f=library/HTMLPurifier/AttrDef"><code>library/HTMLPurifier/AttrDef</code></a>.
 </p>

 <p>
@ -655,7 +655,7 @@ $def = $config-&gt;getHTMLDefinition(true);
 <p class="aside">
  Readers familiar with the modularization may have noticed that the Core
  attribute collection differs from that specified by the <a
-  href="http://www.w3.org/TR/xhtml-modularization/abstract_modules.html#s_commonatts">abstract
+  href="https://www.w3.org/TR/xhtml-modularization/abstract_modules.html#s_commonatts">abstract
  modules of the XHTML Modularization 1.1</a>. We believe this section
  to be in error, as <code>br</code> permits the use of the <code>style</code>
  attribute even though it uses the <code>Core</code> collection, and
@ -676,7 +676,7 @@ $def = $config-&gt;getHTMLDefinition(true);
 <p>
  We're going to implement <code>form</code>. Before we embark, lets
  grab a reference implementation from over at the
-  <a href="http://www.w3.org/TR/html4/sgml/loosedtd.html">transitional DTD</a>:
+  <a href="https://www.w3.org/TR/html4/sgml/loosedtd.html">transitional DTD</a>:
 </p>

 <pre>&lt;!ELEMENT FORM - - (%flow;)* -(FORM)   -- interactive form --&gt;
@ -746,7 +746,7 @@ $form-&gt;excludes = array('form' => true);</strong></pre>
 <p>
  And that's all there is to it! Implementing the rest of the form
  module is left as an exercise to the user; to see more examples
-  check the <a href="http://repo.or.cz/w/htmlpurifier.git?a=tree;hb=HEAD;f=library/HTMLPurifier/HTMLModule"><code>library/HTMLPurifier/HTMLModule/</code></a> directory
+  check the <a href="https://repo.or.cz/w/htmlpurifier.git?a=tree;hb=HEAD;f=library/HTMLPurifier/HTMLModule"><code>library/HTMLPurifier/HTMLModule/</code></a> directory
  in your local HTML Purifier installation.
 </p>

@ -771,8 +771,8 @@ $form-&gt;excludes = array('form' => true);</strong></pre>
 </p>

 <ul>
-  <li><a href="http://repo.or.cz/w/htmlpurifier.git?a=blob;hb=HEAD;f=library/HTMLPurifier/HTMLModule.php"><code>library/HTMLPurifier/HTMLModule.php</code></a></li>
-  <li><a href="http://repo.or.cz/w/htmlpurifier.git?a=blob;hb=HEAD;f=library/HTMLPurifier/ElementDef.php"><code>library/HTMLPurifier/ElementDef.php</code></a></li>
+  <li><a href="https://repo.or.cz/w/htmlpurifier.git?a=blob;hb=HEAD;f=library/HTMLPurifier/HTMLModule.php"><code>library/HTMLPurifier/HTMLModule.php</code></a></li>
+  <li><a href="https://repo.or.cz/w/htmlpurifier.git?a=blob;hb=HEAD;f=library/HTMLPurifier/ElementDef.php"><code>library/HTMLPurifier/ElementDef.php</code></a></li>
 </ul>

 <h2 id="optimized">Notes for HTML Purifier 4.2.0 and earlier</h3>
@ -831,7 +831,7 @@ $purifier = new HTMLPurifier($config);</pre>

 <p>
    <em>Technical notes:</em> ajh pointed out on <a
-        href="http://htmlpurifier.org/phorum/read.php?5,5164,5169#msg-5169">in a forum topic</a> that
+        href="https://htmlpurifier.org/phorum/read.php?5,5164,5169#msg-5169">in a forum topic</a> that
    HTML Purifier appeared to be repeatedly writing to the cache even
    when a cache entry already existed.  Investigation lead to the
    discovery of the following infelicity: caching of customized