Updates links to trafficserver.apache.org to https

README

@@ -152,7 +152,7 @@ plugins to build large scale web applications.
 You can download the latest source code from the official Apache Traffic
 Server site:
 
-       http://trafficserver.apache.org/downloads
+       https://trafficserver.apache.org/downloads
 
 (or via the URL shortener: http://s.apache.org/uG). Once downloaded,
 follow the instructions:
@@ -246,5 +246,5 @@ the installation with
 7. ADDITIONAL INFO
 
   Web page: https://trafficserver.apache.org/
-  Wiki: http://cwiki.apache.org/confluence/display/TS/
+  Wiki: https://cwiki.apache.org/confluence/display/TS/
   User mailing list: [email protected]

README-EC2

@@ -128,7 +128,7 @@ Author: Jason Giedymin
 4.4 How do I contact you for help?
   For mailing lists, and IRC information, visit our web page at
 
-    http://trafficserver.apache.org/
+    https://trafficserver.apache.org/
 
 4.5 Will these AMIs be updated in the future?
   Absolutely!

configure.ac

@@ -35,7 +35,7 @@
 m4_define([TS_VERSION_S],[9.0.0])
 m4_define([TS_VERSION_N],[9000000])
 
-AC_INIT([Apache Traffic Server], TS_VERSION_S(), [[email protected]], [trafficserver],[http://trafficserver.apache.org])
+AC_INIT([Apache Traffic Server], TS_VERSION_S(), [[email protected]], [trafficserver], [https://trafficserver.apache.org])
 AC_PREREQ([2.59])
 AC_CONFIG_AUX_DIR([build/_aux])
 AC_CONFIG_SRCDIR([src/traffic_server/traffic_server.cc])

doc/admin-guide/files/records.config.en.rst

@@ -772,7 +772,7 @@ mptcp
 
 .. note::
 
-   The ``Via`` transaction codes can be decoded with the `Via Decoder Ring <http://trafficserver.apache.org/tools/via>`_.
+   The ``Via`` transaction codes can be decoded with the `Via Decoder Ring <https://trafficserver.apache.org/tools/via>`_.
 
 .. ts:cv:: CONFIG proxy.config.http.request_via_str STRING ApacheTrafficServer/${PACKAGE_VERSION}
    :reloadable:
@@ -798,7 +798,7 @@ mptcp
 
 .. note::
 
-   The ``Via`` transaction code can be decoded with the `Via Decoder Ring <http://trafficserver.apache.org/tools/via>`_.
+   The ``Via`` transaction code can be decoded with the `Via Decoder Ring <https://trafficserver.apache.org/tools/via>`_.
 
 .. ts:cv:: CONFIG proxy.config.http.response_via_str STRING ApacheTrafficServer/${PACKAGE_VERSION}
    :reloadable:
@@ -3634,7 +3634,7 @@ HTTP/2 Configuration
 HTTP/3 Configuration
 ====================
 
-There is no configuration available yet on this release. 
+There is no configuration available yet on this release.
 
 QUIC Configuration
 ====================

doc/admin-guide/logging/examples.en.rst

@@ -33,7 +33,7 @@ Online Event Log Builder
 ========================
 
 If you need any assistance building your event log, you can try out our
-`online log builder <http://trafficserver.apache.org/logbuilder/>`_. This is a
+`online log builder <https://trafficserver.apache.org/logbuilder/>`_. This is a
 work in progress, so any comments, critique or suggestions are most welcome.
 
 Emulating Other HTTP Server Formats

doc/appendices/faq.en.rst

@@ -116,7 +116,7 @@ Please refer to the :ref:`forward-proxy` documentation.
 How do I interpret the Via: header code?
 ----------------------------------------
 
-The ``Via`` header string can be decoded with the `Via Decoder Ring <http://trafficserver.apache.org/tools/via>`_.
+The ``Via`` header string can be decoded with the `Via Decoder Ring <https://trafficserver.apache.org/tools/via>`_.
 
 The Via header is an optional HTTP header added by Traffic Server and other HTTP proxies. If a request goes through multiple proxies, each one appends its Via header content to the end of the existing Via header. Via header content is for general information and diagnostic use only and should not be used as a programmatic interface to Traffic Server. The header is cached by each intermediary with the object as received from its downstream node. Thus, the last node in the list to report a cache hit is the end of the transaction for that specific request. Nodes reported earlier were from a previous transaction.
 

doc/doap.rdf

@@ -21,18 +21,18 @@
     See the License for the specific language governing permissions and
     limitations under the License.
 -->
-  <Project rdf:about="http://trafficserver.apache.org">
+  <Project rdf:about="https://trafficserver.apache.org">
     <created>2011-04-08</created>
     <license rdf:resource="http://usefulinc.com/doap/licenses/asl20" />
     <name>Apache Traffic Server</name>
-    <homepage rdf:resource="http://trafficserver.apache.org" />
-    <asfext:pmc rdf:resource="http://trafficserver.apache.org" />
+    <homepage rdf:resource="https://trafficserver.apache.org" />
+    <asfext:pmc rdf:resource="https://trafficserver.apache.org" />
     <shortdesc>Apache Traffic Server is an HTTP proxy cache.</shortdesc>
     <description>Apache Traffic Server is fast, scalable and extensible HTTP/1.1 compliant caching proxy server. ATS can be used as a reverse, forward or even transparent HTTP proxy.
     </description>
-    <bug-database rdf:resource="https://issues.apache.org/jira/browse/TS" />
-    <mailing-list rdf:resource="http://trafficserver.apache.org/" />
-    <download-page rdf:resource="http://trafficserver.apache.org/downloads.html" />
+    <bug-database rdf:resource="https://github.com/apache/trafficserver/issues" />
+    <mailing-list rdf:resource="https://trafficserver.apache.org/" />
+    <download-page rdf:resource="https://trafficserver.apache.org/downloads.html" />
     <programming-language>C++</programming-language>
     <category rdf:resource="http://projects.apache.org/category/http" />
     <release>

tools/trafficserver.pc.in

@@ -16,7 +16,7 @@
 
 Name: trafficserver
 Description: The @PACKAGE_NAME@ caching HTTP proxy server
-URL: http://trafficserver.apache.org/
+URL: https://trafficserver.apache.org/
 Version: @PACKAGE_VERSION@
 
 prefix=@prefix@