update links

jmckenna · jmckenna · commit 28d9625e7c0f · 2025-04-14T10:02:10.000-03:00
diff --git a/en/development/announce/6-2.txt b/en/development/announce/6-2.txt
@@ -457,7 +457,7 @@ with binaries for the new release shortly.
 Thanks
 ------
 
-The MapServer team would like to thank `Météo-France <http://en.wikipedia.org/wiki/Météo-France>`_
+The MapServer team would like to thank `Météo-France <https://en.wikipedia.org/wiki/Météo-France>`_
 for funding a number of the new features present in this release.
 
 Finally, thank you to all of the users, developers, and supporters of MapServer. Enjoy!
diff --git a/en/development/rfc/ms-rfc-108.txt b/en/development/rfc/ms-rfc-108.txt
@@ -22,7 +22,7 @@ each sample of the sparse dataset. They are usually represented with a
 color-ramp where the hue encodes the density of the data sample, optionally
 along with the intensity of an attribute. The "heatmap" term itself is used 
 with varying meanings; in the context of this RFC, we will be using it to
-reference `Kernel Density Estimation <http://en.wikipedia.org/wiki/Multivariate_kernel_density_estimation>`_
+reference `Kernel Density Estimation <https://en.wikipedia.org/wiki/Multivariate_kernel_density_estimation>`_
 maps.
 
 .. figure:: ../../images/heatmap-wikipedia.png
diff --git a/en/development/rfc/ms-rfc-113.txt b/en/development/rfc/ms-rfc-113.txt
@@ -4,7 +4,7 @@
 MS RFC 113: Layer Compositing Pipeline
 ======================================
 
-:Date:  2015/02
+:Date:  2015-02
 :Author: Thomas Bonfort
 :Contact: thomas.bonfort@gmail.com
 :Status: Implemented
@@ -15,7 +15,7 @@ MS RFC 113: Layer Compositing Pipeline
 
 Some cartographic renderings would benefit from the addition of advanced
 blending modes, as can be explained in detail in
-http://en.wikipedia.org/wiki/Blend_modes . In particular, this functionality is
+https://en.wikipedia.org/wiki/Blend_modes . In particular, this functionality is
 essential for more pleasant renderings of raster hillshadings over vector
 surfaces.
 
diff --git a/en/development/rfc/ms-rfc-24-FIRSTDRAFT.txt b/en/development/rfc/ms-rfc-24-FIRSTDRAFT.txt
@@ -24,7 +24,7 @@ Memory management in SWIG wrappers has a tradition of being difficult and error
 Most modern languages implement garbage collection, so that the developer does not have to care about memory management.
 The programming language tracks memory (or objects, really) allocations and when an object goes out of scope (it is no more reachable from the running program) it marks it as eligible for garbage collection. A background process once in a while wakes up and frees the memory associated with marked objects.
 For the details on GC see this wikipedia entry:
-http://en.wikipedia.org/wiki/Garbage_collection_(computer_science)
+https://en.wikipedia.org/wiki/Garbage_collection_(computer_science)
 
 What happens in most cases is that some memory is allocated in, say, Java, then another pointer is
 pointed to it by invoking some wrapped method.
diff --git a/en/development/rfc/ms-rfc-24.txt b/en/development/rfc/ms-rfc-24.txt
@@ -208,7 +208,7 @@ keyed by memory address. This will eliminate the need for a change to *every*
 object but might present a greater impact on performance. In particular the 
 hash function must be chosen carefully.
 
-http://en.wikipedia.org/wiki/Hash_table
+https://en.wikipedia.org/wiki/Hash_table
 
 The example implementation proposed at the tracker `bug #2032`_ adopts the 
 first strategy.
diff --git a/en/development/rfc/ms-rfc-76.txt b/en/development/rfc/ms-rfc-76.txt
@@ -150,7 +150,7 @@ The ability to use the XMP facility across output drivers would be desirable, bu
  +1 Mike Smith
 
 
-.. [1] http://en.wikipedia.org/wiki/Extensible_Metadata_Platform
+.. [1] https://en.wikipedia.org/wiki/Extensible_Metadata_Platform
 .. [2] http://www.adobe.com/products/xmp/overview.html
 .. [3] http://wiki.creativecommons.org/XMP
 .. [4] http://libopenraw.freedesktop.org/wiki/Exempi
diff --git a/en/development/rfc/ms-rfc-78.txt b/en/development/rfc/ms-rfc-78.txt
@@ -23,7 +23,7 @@ values at a given location we can compute a rotation and magnitude and use
 that to draw an arrow of a size proportional to the magnitude and pointing
 in the direction of the phenomenon (wind, current, etc.)
 
-For more details about vector fields, refer to: http://en.wikipedia.org/wiki/Vector_field 
+For more details about vector fields, refer to: https://en.wikipedia.org/wiki/Vector_field 
 
 Visual example (rendered with MapServer):
 
diff --git a/en/development/rfc/ms-rfc-85.txt b/en/development/rfc/ms-rfc-85.txt
@@ -16,7 +16,7 @@ MS RFC 85: Vector Contour Rendering (CONNECTIONTYPE CONTOUR)
 This is a proposal to add the ability to compute and render contour layers on
 the fly in MapServer from a raster source. The source is one band of raster
 data, which represents a digital elevation model (DEM). More info about DEMs at:
-http://en.wikipedia.org/wiki/Digital_elevation_model
+https://en.wikipedia.org/wiki/Digital_elevation_model
 
 Contours can already be rendered today using a standard vector layer but this
 requires an extra processing step with gdal_contour to pre-generate the contours
diff --git a/en/development/rfc/ms-rfc-90.txt b/en/development/rfc/ms-rfc-90.txt
@@ -53,7 +53,7 @@ by spaces or newlines)
   END
 
   
-We can also specify IP ranges using the `CIDR notation <http://en.wikipedia.org/wiki/CIDR_notation>`_ , like: "192.168.1.0/24"
+We can also specify IP ranges using the `CIDR notation <https://en.wikipedia.org/wiki/Classless_Inter-Domain_Routing#CIDR_notation>`_ , like: "192.168.1.0/24"
 
 Setting ows_allowed_ip_list will deny all other IPs not specified in the list, and setting ows_denied_ip_list will allow all other IPs not specified in the list. When we both allow and deny a given IP the denial will take precedence.
 
diff --git a/en/development/rfc/ms-rfc-98.txt b/en/development/rfc/ms-rfc-98.txt
@@ -63,7 +63,7 @@ languages, it has a number of shortcomings that this RFC aims to resolve:
 - While latin languages have a 1-to-1 mapping between string characters and font glyphs,
   this is not the case for complex languages, where ligature glyphs need to be inserted
   depending on context (see the `wikipedia complex text layout page
-  <http://en.wikipedia.org/wiki/Complex_text_layout>`_ for a more complete explanation).
+  <https://en.wikipedia.org/wiki/Complex_text_layout>`_ for a more complete explanation).
   While this is partly taken care of for us by fribidi for arabic (which has a shaping
   algorithm that inserts ligatures for us), we currently fail hard for other complex
   text languages.
diff --git a/en/faq.txt b/en/faq.txt
@@ -617,8 +617,8 @@ The MapServer logo illustrates the confluence of the `Minnesota`_ and `Mississip
 rivers, quite near to the home of the `St. Paul Campus`_ of the `University of Minnesota`_, which 
 was the `birthplace of MapServer`_.
 
-.. _`Minnesota`: http://en.wikipedia.org/wiki/Minnesota_River
-.. _`Mississippi`: http://en.wikipedia.org/wiki/Mississippi_River
-.. _`St. Paul Campus`: http://en.wikipedia.org/wiki/University_of_Minnesota#St._Paul_campus
-.. _`University of Minnesota`: http://en.wikipedia.org/wiki/University_of_Minnesota
+.. _`Minnesota`: https://en.wikipedia.org/wiki/Minnesota_River
+.. _`Mississippi`: https://en.wikipedia.org/wiki/Mississippi_River
+.. _`St. Paul Campus`: https://en.wikipedia.org/wiki/University_of_Minnesota#St._Paul_campus
+.. _`University of Minnesota`: https://en.wikipedia.org/wiki/University_of_Minnesota
 .. _`birthplace of MapServer`: https://lists.osgeo.org/pipermail/mapserver-dev/2009-December/009435.html 
diff --git a/en/glossary.txt b/en/glossary.txt
@@ -43,7 +43,7 @@
     FreeType
         `FreeType <http://freetype.sourceforge.net/index2.html>`__ is a font
         engine that MapServer uses for accessing and rendering `TrueType
-        <http://en.wikipedia.org/wiki/True_Type_Font>`__ fonts.
+        <https://en.wikipedia.org/wiki/True_Type_Font>`__ fonts.
         
     GD
         `GD <https://libgd.github.io/>`__ is a graphics library for 
@@ -78,7 +78,7 @@
             :ref:`wfs_server`
 
     GPX
-        `GPS eXchange <http://en.wikipedia.org/wiki/GPX_(data_transfer)>`__
+        `GPS eXchange <https://en.wikipedia.org/wiki/GPX_(data_transfer)>`__
         Format is an XML Schema for describing GPS data.  :term:`OGR` can
         be used to transform and render this data with MapServer.
 
@@ -99,7 +99,7 @@
     
     Mercator
         Wikipedia provides excellent coverage of the 
-        `Mercator projection <http://en.wikipedia.org/wiki/Mercator_projection>`_.
+        `Mercator projection <https://en.wikipedia.org/wiki/Mercator_projection>`_.
 
     OGC
         The `Open Geospatial Consortium <https://www.ogc.org>`_ is a
diff --git a/en/input/vector/contour.txt b/en/input/vector/contour.txt
@@ -13,7 +13,7 @@ Contour
 MapServer (since version 6.4) can compute and render a contour layer on the 
 fly from a raster source.  The raster source is one band of raster data, which
 represents a digital elevation model (DEM).  More info about DEMs at:
-http://en.wikipedia.org/wiki/Digital_elevation_model
+https://en.wikipedia.org/wiki/Digital_elevation_model
 
 2. How it works
 ------------------------
diff --git a/en/mapfile/composite.txt b/en/mapfile/composite.txt
@@ -56,7 +56,7 @@ COMPFILTER [string]
 
 COMPOP [string]
     Name of the compositing operator to use when blending the temporary image
-    onto the main map image. See `http://en.wikipedia.org/wiki/Blend_modes`.
+    onto the main map image. See `https://en.wikipedia.org/wiki/Blend_modes`.
     The default compositing operator is "src-over".
 
     Available operators are:
@@ -265,4 +265,4 @@ the value `darken`:
   END # LAYER
 
 
-.. _`Blend Modes`: http://en.wikipedia.org/wiki/Blend_modes
+.. _`Blend Modes`: https://en.wikipedia.org/wiki/Blend_modes
diff --git a/en/mapfile/xmp_metadata.txt b/en/mapfile/xmp_metadata.txt
@@ -22,7 +22,7 @@ embed the license information in the image file using a common
 metadata standard.
 
 XMP is the "`extensible metadata platform
-<http://en.wikipedia.org/wiki/Extensible_Metadata_Platform>`_" which
+<https://en.wikipedia.org/wiki/Extensible_Metadata_Platform>`_" which
 allows the embedding of metadata information across a wide range of
 document and image formats: PNG, GIF, JPEG, PDF, etc. XMP was
 originally developed by `Adobe
diff --git a/en/output/kerneldensity.txt b/en/output/kerneldensity.txt
@@ -292,4 +292,4 @@ each sample:
 
 
 
-.. _`Kernel Density Estimation`: http://en.wikipedia.org/wiki/Multivariate_kernel_density_estimation
+.. _`Kernel Density Estimation`: https://en.wikipedia.org/wiki/Multivariate_kernel_density_estimation
