more http->https changes for both the wiki and the commitfest-app

templates/docs/index.html

@@ -11,7 +11,7 @@ <h1>Documentation</h1>
 
 <p>You can learn <a href="/docs/9.3/static/release-9-3.html">what's new</a> in the latest release, and view a listing of <a href="/docs/books">books</a>
 written about PostgreSQL (some of which are available in their entirety online).
-<a href="http://wiki.postgresql.org">Technical documentation</a> is also available in this section, or you can check <a href="/support/security">Security Information</a>.</p>
+<a href="https://wiki.postgresql.org">Technical documentation</a> is also available in this section, or you can check <a href="/support/security">Security Information</a>.</p>
 
 </div>
 </div>

templates/downloads/ftpbrowser.html

@@ -20,7 +20,7 @@ <h2>Files</h2>
 <div id="pgFtpContent">
 <table border="0" cellpadding="0" cellspacing="0" width="90%">
 {%for file in files%}
-<tr><td><a href="http://ftp.postgresql.org/pub/{{basepath}}/{{file.name}}"><img src="/media/img/ftp/file.png" alt="{{file.name}}" /></a>&nbsp;<a href="http://ftp.postgresql.org/pub/{{basepath}}/{{file.name}}">{{file.name}}</a></td><td>{{file.mtime}}</td><td>{{file.size|filesizeformat}}</td></tr>
+<tr><td><a href="https://ftp.postgresql.org/pub/{{basepath}}/{{file.name}}"><img src="/media/img/ftp/file.png" alt="{{file.name}}" /></a>&nbsp;<a href="https://ftp.postgresql.org/pub/{{basepath}}/{{file.name}}">{{file.name}}</a></td><td>{{file.mtime}}</td><td>{{file.size|filesizeformat}}</td></tr>
 {%endfor%}
 </table>
 </div>

templates/index.html

@@ -66,7 +66,7 @@ <h2><img src="/media/img/hdr/hdr_shortcuts.png" width="85" height="10" alt="Shor
                   <a href="/community/lists">Mailing Lists</a>
                 </li>
                 <li>
-                  <a href="http://wiki.postgresql.org/">Wiki</a>
+                  <a href="https://wiki.postgresql.org/">Wiki</a>
                 </li>
                 <li>
                   <a href="/support/submitbug">Report a Bug</a>

templates/misc/bug_header.html

@@ -12,8 +12,8 @@
 bug either, unless compliance for the specific feature is explicitly claimed.</p>
 
 <p>Before you continue, check on the
-<a href="http://wiki.postgresql.org/wiki/Todo">TODO list</a> and in the
-<a href="http://wiki.postgresql.org/wiki/Category:FAQ">FAQ</a> to see if your bug is already known. If you cannot
+<a href="https://wiki.postgresql.org/wiki/Todo">TODO list</a> and in the
+<a href="https://wiki.postgresql.org/wiki/Category:FAQ">FAQ</a> to see if your bug is already known. If you cannot
 decode the information on the TODO list, report your problem so we can clarify
 the TODO list.</p>
 

templates/pages/about/advantages.html

@@ -41,7 +41,7 @@ <h2>Designed for high volume environments</h2>
 
 <a name="gui"></a>
 <h2>GUI database design and administration tools</h2>
-<p>There are many high-quality GUI Tools available for PostgreSQL from both open source developers and commercial providers. A list is available on our wiki as  a <a href="http://wiki.postgresql.org/wiki/Community_Guide_to_PostgreSQL_GUI_Tools">community guide</a> to PostgreSQL GUI Tools. 
+<p>There are many high-quality GUI Tools available for PostgreSQL from both open source developers and commercial providers. A list is available on our wiki as  a <a href="https://wiki.postgresql.org/wiki/Community_Guide_to_PostgreSQL_GUI_Tools">community guide</a> to PostgreSQL GUI Tools. 
 
 <a name="features"></a>
 <h2>Technical Features</h2>

templates/pages/about/donate_pg_org.html

@@ -4,7 +4,7 @@
 
 <h1>Donate to PostgreSQL</h1>
 
-<p>PostgreSQL donations are managed by the <a href="http://wiki.PostgreSQL.org/wiki/SponsorShip">Fund raising Group</a>. The money donated goes to many vital services that the PostgreSQL community needs including advocacy materials, conference expenses, legal expenses, and travel costs.</p>
+<p>PostgreSQL donations are managed by the <a href="https://wiki.PostgreSQL.org/wiki/SponsorShip">Fund raising Group</a>. The money donated goes to many vital services that the PostgreSQL community needs including advocacy materials, conference expenses, legal expenses, and travel costs.</p>
 
 <h3>Donate by Credit Card (preferred)</h3>
 <p>Donation via credit card is handled through USA ePay using the form below. 

templates/pages/developer.html

@@ -15,9 +15,9 @@ <h2>Who are we?</h2>
 <h2>What will you find here?</h2>
 
 <p>The information available in this section will mainly interest PostgreSQL developers. Here you'll find the
-<a href="/developer/roadmap">roadmap</a> with current <a href="http://wiki.postgresql.org/wiki/Todo">TODO list</a>, <a href="/developer/coding">coding</a> and
+<a href="/developer/roadmap">roadmap</a> with current <a href="https://wiki.postgresql.org/wiki/Todo">TODO list</a>, <a href="/developer/coding">coding</a> and
 <a href="/developer/testing">testing</a> information, <a href="/community/lists#developer">mailing lists</a>, and
-the developer <a href="http://wiki.postgresql.org/wiki/Developer_FAQ">FAQ</a>. Keep in mind the information available here is not 
+the developer <a href="https://wiki.postgresql.org/wiki/Developer_FAQ">FAQ</a>. Keep in mind the information available here is not
 necessarily available in the release version of PostgreSQL - it may not yet even be in the development version.
 </p>
 

templates/pages/developer/alpha.html

@@ -15,7 +15,7 @@ <h1>Alpha Information</h1>
 </p>
 <p>
 The development cycle of a PostgreSQL major release alternates between
-periods of development and periods of integration work, called <a href="http://commitfest.postgresql.org/">commit
+periods of development and periods of integration work, called <a href="https://commitfest.postgresql.org/">commit
 fests</a>, normally one month each.  Alpha releases are planned to be
 produced at the end of every commit fest, thus every two months.
 Since the first commit fest starts within a month from the beginning
@@ -28,5 +28,5 @@ <h1>Alpha Information</h1>
 <p>We depend on our large community of users to test the features in alpha
  releases and report issues.  If you are able to contribute to PostgreSQL by
 doing alpha testing, please see our 
-<a href="http://wiki.postgresql.org/wiki/HowToBetaTest">Alpha/Beta Testing Page.</a></p>
+<a href="https://wiki.postgresql.org/wiki/HowToBetaTest">Alpha/Beta Testing Page.</a></p>
 {%endblock%}

templates/pages/developer/backend.html

@@ -6,7 +6,7 @@ <h1>Backend Flowchart</h1>
 
 <center>
 <h3><i>Click on an item</i> to see more detail or look at the full
-<a href="http://wiki.postgresql.org/wiki/Backend_flowchart">index.</a></h3>
+<a href="https://wiki.postgresql.org/wiki/Backend_flowchart">index.</a></h3>
 
 <p><img src="../../../media/img/developer/backend/flow.gif" usemap="#flowmap" alt="flowchart" />
 
@@ -17,34 +17,34 @@ <h3><i>Click on an item</i> to see more detail or look at the full
  -->
 
 <map name="flowmap" id="flowmap">
-<area coords="50, 0, 195, 45" href="http://wiki.postgresql.org/wiki/Backend_flowchart#main" alt="main" />
-<area coords="50, 65,  195, 110" href="http://wiki.postgresql.org/wiki/Backend_flowchart#postmaster" alt="postmaster" />
-<area coords="50, 135, 195, 180" href="http://wiki.postgresql.org/wiki/Backend_flowchart#tcop" alt="tcop" />
-<area coords="50, 225, 195, 270" href="http://wiki.postgresql.org/wiki/Backend_flowchart#parser" alt="parser" />
-<area coords="50, 295, 195, 340" href="http://wiki.postgresql.org/wiki/Backend_flowchart#tcop" alt="tcop" />
-<area coords="50, 365, 195, 410" href="http://wiki.postgresql.org/wiki/Backend_flowchart#rewrite" alt="rewrite" />
-<area coords="50, 435, 195, 480" href="http://wiki.postgresql.org/wiki/Backend_flowchart#optimizer_path" alt="path" />
-<area coords="50, 505, 195, 550" href="http://wiki.postgresql.org/wiki/Backend_flowchart#optimizer_plan" alt="plan" />
-<area coords="50, 575, 195, 620" href="http://wiki.postgresql.org/wiki/Backend_flowchart#executor" alt="executor" />
-
-<area coords="280, 35, 425, 80" href="http://wiki.postgresql.org/wiki/Backend_flowchart#libpq" alt="libpq" />
-<area coords="280, 135, 425, 180" href="http://wiki.postgresql.org/wiki/Backend_flowchart#tcop" alt="tcop" />
-<area coords="280, 285, 425, 330" href="http://wiki.postgresql.org/wiki/Backend_flowchart#commands" alt="commands" />
-
-<area coords="0, 710, 145, 755" href="http://wiki.postgresql.org/wiki/Backend_flowchart#utils" alt="utils" />
-<area coords="190, 710, 335, 755" href="http://wiki.postgresql.org/wiki/Backend_flowchart#catalog" alt="catalog" />
-<area coords="365, 710, 510, 755" href="http://wiki.postgresql.org/wiki/Backend_flowchart#storage" alt="storage" />
-
-<area coords="85, 780, 230, 825" href="http://wiki.postgresql.org/wiki/Backend_flowchart#access" alt="access" />
-<area coords="280, 780, 425, 825" href="http://wiki.postgresql.org/wiki/Backend_flowchart#nodes" alt="nodes" />
+<area coords="50, 0, 195, 45" href="https://wiki.postgresql.org/wiki/Backend_flowchart#main" alt="main" />
+<area coords="50, 65,  195, 110" href="https://wiki.postgresql.org/wiki/Backend_flowchart#postmaster" alt="postmaster" />
+<area coords="50, 135, 195, 180" href="https://wiki.postgresql.org/wiki/Backend_flowchart#tcop" alt="tcop" />
+<area coords="50, 225, 195, 270" href="https://wiki.postgresql.org/wiki/Backend_flowchart#parser" alt="parser" />
+<area coords="50, 295, 195, 340" href="https://wiki.postgresql.org/wiki/Backend_flowchart#tcop" alt="tcop" />
+<area coords="50, 365, 195, 410" href="https://wiki.postgresql.org/wiki/Backend_flowchart#rewrite" alt="rewrite" />
+<area coords="50, 435, 195, 480" href="https://wiki.postgresql.org/wiki/Backend_flowchart#optimizer_path" alt="path" />
+<area coords="50, 505, 195, 550" href="https://wiki.postgresql.org/wiki/Backend_flowchart#optimizer_plan" alt="plan" />
+<area coords="50, 575, 195, 620" href="https://wiki.postgresql.org/wiki/Backend_flowchart#executor" alt="executor" />
+
+<area coords="280, 35, 425, 80" href="https://wiki.postgresql.org/wiki/Backend_flowchart#libpq" alt="libpq" />
+<area coords="280, 135, 425, 180" href="https://wiki.postgresql.org/wiki/Backend_flowchart#tcop" alt="tcop" />
+<area coords="280, 285, 425, 330" href="https://wiki.postgresql.org/wiki/Backend_flowchart#commands" alt="commands" />
+
+<area coords="0, 710, 145, 755" href="https://wiki.postgresql.org/wiki/Backend_flowchart#utils" alt="utils" />
+<area coords="190, 710, 335, 755" href="https://wiki.postgresql.org/wiki/Backend_flowchart#catalog" alt="catalog" />
+<area coords="365, 710, 510, 755" href="https://wiki.postgresql.org/wiki/Backend_flowchart#storage" alt="storage" />
+
+<area coords="85, 780, 230, 825" href="https://wiki.postgresql.org/wiki/Backend_flowchart#access" alt="access" />
+<area coords="280, 780, 425, 825" href="https://wiki.postgresql.org/wiki/Backend_flowchart#nodes" alt="nodes" />
 </map>
 </center>
 
 <br />
 
 <p>A query comes to the backend via data packets arriving through TCP/IP
 or Unix Domain sockets. It is loaded into a string, and passed to the <a
-href="http://wiki.postgresql.org/wiki/Backend_flowchart#parser">parser,</a>
+href="https://wiki.postgresql.org/wiki/Backend_flowchart#parser">parser,</a>
 where the lexical scanner, <a
 href="http://git.postgresql.org/gitweb/?p=postgresql.git;a=blob;f=src/backend/parser/scan.l">scan.l,</a>
 breaks the query up into tokens(words). The parser uses <a
@@ -58,7 +58,7 @@ <h3><i>Click on an item</i> to see more detail or look at the full
 <p>The statement is then identified as complex (<i>SELECT / INSERT /
 UPDATE / DELETE</i>) or a simple, e.g <i> CREATE USER, ANALYZE, </i>,
 etc.  Simple utility commands are processed by statement-specific
-functions in <a href="http://wiki.postgresql.org/wiki/Backend_flowchart#commands.</a>
+functions in <a href="https://wiki.postgresql.org/wiki/Backend_flowchart#commands.</a>
 Complex statements require more handling.</p>
 
 <p>The parser takes a complex query, and creates a <a
@@ -89,21 +89,21 @@ <h3><i>Click on an item</i> to see more detail or look at the full
 
 <p>The next step is for the Query to be modified by any
 <i>VIEWS</i> or <i>RULES</i> that may apply to the query. This is
-performed by the <a href="http://wiki.postgresql.org/wiki/Backend_flowchart#rewrite">rewrite</a>
+performed by the <a href="https://wiki.postgresql.org/wiki/Backend_flowchart#rewrite">rewrite</a>
 system.</p>
 
 <p>The <a
-href="http://wiki.postgresql.org/wiki/Backend_flowchart#optimizer_path">optimizer</a>
+href="https://wiki.postgresql.org/wiki/Backend_flowchart#optimizer_path">optimizer</a>
 uses the Query structure to determine the best table join order and join
 type of each table in the RangeTable, using Query.qual(<i>WHERE</i>
 clause) to consider optimal index usage.</p>  The <a
-href="http://wiki.postgresql.org/wiki/Backend_flowchart#optimizer_path">path</a>
+href="https://wiki.postgresql.org/wiki/Backend_flowchart#optimizer_path">path</a>
 module  then generates an optimal <a
-href="http://git.postgresql.org/gitweb/?p=postgresql.git;a=blob;f=src/include/nodes/plannodes.h">Plan,</a>
+href="https://git.postgresql.org/gitweb/?p=postgresql.git;a=blob;f=src/include/nodes/plannodes.h">Plan,</a>
 which contains the operations to be performed to execute the query.
 
 <p>The Plan is then passed to the <a
-href="http://wiki.postgresql.org/wiki/Backend_flowchart#executor">executor</a> for execution, and the
+href="https://wiki.postgresql.org/wiki/Backend_flowchart#executor">executor</a> for execution, and the
 result returned to the client. The Plan is actually as set of nodes,
 arranged in a tree structure with a top-level node, and various
 sub-nodes as children.</p>

templates/pages/developer/beta.html

@@ -20,7 +20,7 @@ <h1>Beta Information</h1>
   </li>
 
   <li>
-    <a href="http://wiki.postgresql.org/wiki/HowToBetaTest">A Guide on PostgreSQL Beta Testing</a>
+    <a href="https://wiki.postgresql.org/wiki/HowToBetaTest">A Guide on PostgreSQL Beta Testing</a>
   </li>
 </ul>
 {%endblock%}

templates/pages/developer/coding.html

@@ -12,8 +12,8 @@ <h2>Code access and information</h2>
     <li><a href="/docs/current/static/git.html">Information about the Source Code Repository</a></li>
     <li><a href="http://doxygen.postgresql.org/">Source Code Browser</a> (Doxygen)</li>
     <li><a href="/developer/backend/">Backend Flowchart</a></li>
-    <li><a href="http://babel.postgresql.org/">Translating</a></li>
-    <li><a href="http://wiki.postgresql.org/wiki/Developer_and_Contributor_Resources">Developer Section on wiki.postgresql.org</a></li>
+    <li><a href="https://babel.postgresql.org/">Translating</a></li>
+    <li><a href="https://wiki.postgresql.org/wiki/Developer_and_Contributor_Resources">Developer Section on wiki.postgresql.org</a></li>
     <li>
      <form action="http://git.postgresql.org/gitweb" method="get">
       <input type="hidden" name="p" value="postgresql.git" />
@@ -26,7 +26,7 @@ <h2>Code access and information</h2>
 
 <h2>Documentation</h2>
 <ul>
-    <li><a href="http://wiki.postgresql.org/wiki/Developer_FAQ">Frequently Asked Questions for Developers</a></li>
+    <li><a href="https://wiki.postgresql.org/wiki/Developer_FAQ">Frequently Asked Questions for Developers</a></li>
 </ul>
 
 <h2>Presentations</h2>

templates/pages/developer/roadmap.html

@@ -17,9 +17,9 @@ <h1>Roadmap</h1>
 are several places you can look to find out more information on upcoming
 features:</p>
 <dl>
-	<dt>General <a href="http://wiki.postgresql.org/wiki/Development_information">development information</a></dt>
+	<dt>General <a href="https://wiki.postgresql.org/wiki/Development_information">development information</a></dt>
 	<dd>A wiki page about various aspects of the PostgreSQL development process</dd>
-	<dt>Information about the current <a href="http://commitfest.postgresql.org/">commit fest</a></dt>
+	<dt>Information about the current <a href="https://commitfest.postgresql.org/">commit fest</a></dt>
 	<dd>An overview about the status on patches for the current commitfest</dd>
 </dl>
 

templates/pages/developer/summerofcode.html

@@ -25,9 +25,9 @@ <h2>Example Proposal Ideas</h2>
 <p>The PostgreSQL Project has a wide range of opinions on what it feels are acceptable GSoC projects. The examples listed here are meant only as a suggestion of things we would likely find useful, but you should not feel obligated to pick from this list by any means. If you have just discovered a new algorithm as part of your thesis work, we would love to see a proposal implementing that in PostgreSQL. The point is that all proposals will be evaluated on their own merits, so be creative.
 
 <ul>
-<li><strong>TODO Items</strong>: A number of the items on our TODO list have been marked as good projects for beginners who are new to the PostgreSQL code. Items on this list have the advantage of already having general community agreement that the feature is desireable. These items should also have some general discussion available in the mailing list archives to help get you started. You can find these items on the <a href="http://wiki.postgresql.org/wiki/Todo">TODO</a> list, they will be marked with an [E].
+<li><strong>TODO Items</strong>: A number of the items on our TODO list have been marked as good projects for beginners who are new to the PostgreSQL code. Items on this list have the advantage of already having general community agreement that the feature is desireable. These items should also have some general discussion available in the mailing list archives to help get you started. You can find these items on the <a href="https://wiki.postgresql.org/wiki/Todo">TODO</a> list, they will be marked with an [E].
 </li>
-<li><strong>Other Ideas</strong>: are given on our <a href="http://wiki.postgresql.org/wiki/GSoC_2014#Project_Ideas">GSoC 2014 Wiki Page</a></li>
+<li><strong>Other Ideas</strong>: are given on our <a href="https://wiki.postgresql.org/wiki/GSoC_2014#Project_Ideas">GSoC 2014 Wiki Page</a></li>
 
 <a id="mentors" name="mentors"></a>
 <h2>Mentors</h2>
@@ -39,7 +39,7 @@ <h2>Mentors</h2>
 	<li>Josh Berkus &lt;josh @t postgresql.org&gt;, PostgreSQL Experts, performance engineering</li>
 </ul>
 
-<p>A list of prospective mentors will be provided on our <a href="http://wiki.postgresql.org/wiki/GSoC_2014#2014_Mentors">GSoC 2014 Wiki Page</a></p>
+<p>A list of prospective mentors will be provided on our <a href="https://wiki.postgresql.org/wiki/GSoC_2014#2014_Mentors">GSoC 2014 Wiki Page</a></p>
 
 <p>If your project is not selected for funding by Google, but you still think you have a
 feasible project proposal, then please email our developers mailing list at <a
@@ -89,10 +89,10 @@ <h2>Previously Accepted Projects</h2>
 
 <p>More information on these projects can be found on Google's PostgreSQL SoC pages: 
 (
-<a href="http://wiki.postgresql.org/wiki/GSoC_2013">2013</a>
- | <a href="http://wiki.postgresql.org/wiki/GSoC_2012">2012</a>
- | <a href="http://wiki.postgresql.org/wiki/GSoC_2011">2011</a>
- | <a href="http://wiki.postgresql.org/wiki/GSoC_2010">2010</a>
+<a href="https://wiki.postgresql.org/wiki/GSoC_2013">2013</a>
+ | <a href="https://wiki.postgresql.org/wiki/GSoC_2012">2012</a>
+ | <a href="https://wiki.postgresql.org/wiki/GSoC_2011">2011</a>
+ | <a href="https://wiki.postgresql.org/wiki/GSoC_2010">2010</a>
  | <a href="http://code.google.com/soc/2008/postgres/about.html">2008</a>
  | <a href="http://code.google.com/soc/2008/postgres/about.html">2007</a>
  | <a href="http://code.google.com/soc/2006/pgsql/about.html">2006</a>)</p>

templates/pages/docs/faq.html

@@ -7,13 +7,13 @@ <h1>Frequently Asked Questions</h1>
 <h2>General</h2>
 
 <ul>
-<li><a href="http://wiki.postgresql.org/wiki/FAQ">PostgreSQL FAQ</a></li>
-<li><a href="http://wiki.postgresql.org/wiki/Developer_FAQ">Developer's FAQ</a></li>
+<li><a href="https://wiki.postgresql.org/wiki/FAQ">PostgreSQL FAQ</a></li>
+<li><a href="https://wiki.postgresql.org/wiki/Developer_FAQ">Developer's FAQ</a></li>
 </ul>
 
 <h2>Other FAQs</h2>
 <p>
 There are several more platform-specific and language-specific FAQs available on
-<a href="http://wiki.postgresql.org/wiki/Category:FAQ">our wiki</a>.
+<a href="https://wiki.postgresql.org/wiki/Category:FAQ">our wiki</a>.
 </p>
 {%endblock%}