MapServer Version Information

MapServer version 8.1.0-dev (MS4W 5.0.0) PROJ version 9.3
GDAL version 3.8 OUTPUT=PNG OUTPUT=JPEG OUTPUT=KML SUPPORTS=PROJ
SUPPORTS=AGG SUPPORTS=FREETYPE SUPPORTS=CAIRO SUPPORTS=SVG_SYMBOLS
SUPPORTS=SVGCAIRO SUPPORTS=ICONV SUPPORTS=FRIBIDI SUPPORTS=WMS_SERVER
SUPPORTS=WMS_CLIENT SUPPORTS=WFS_SERVER SUPPORTS=WFS_CLIENT
SUPPORTS=WCS_SERVER SUPPORTS=SOS_SERVER SUPPORTS=OGCAPI_SERVER
SUPPORTS=FASTCGI SUPPORTS=THREADS SUPPORTS=GEOS SUPPORTS=PBF
INPUT=JPEG INPUT=POSTGIS INPUT=OGR INPUT=GDAL INPUT=SHAPEFILE
INPUT=FLATGEOBUF

MapServer Build Environment

Compiled, packaged, documented, and tested by GatewayGeo. Please help support this great product that is downloaded over 6,000 times a month by organizations of all sizes - please contact us directly at info@gatewaygeomatics.com for custom builds or requests. Thank you in advance for your generous support!

Library versions used to build this version of MapServer:

apache-ant-1.7.0
apr-1.7.4
apr-iconv-1.2.2
apr-util-1.6.3
berkeley-db-18.1.40
bzip2-1.0.6
boost-1.77.0
brotli-1.0.10-dev
cairo-1.16.0
crypto++-git-master-2023-05-22
curl-8.3.0
expat-2.5.0
fcgi-2.4.0
fits-4.2.0
freetype-2.13.2
freexl-2.0.0
fribidi-1.0.13
gdal-3.8.0-dev
geos-3.12.0
gettext-runtime-0.17-source
giflib-5.2.1
harfbuzz-3.4.0
hdf-4.2.16
hdf5-1.14.1
httpd-2.4.57
jansson-2.15-dev
jbigkit-1.6
json-c-0.16
kealib-1.5.1
lerc-git-2021-09-17
libdeflate-1.18
libecwj2-3.3
libgeotiff-1.7.1
libiconv-1.16
libjpeg-turbo-3.0.0
libkml-git-2023-02-19
libpng-1.6.40
librttopo-1.1.0
libspatialite-5.1-dev
libsvg-0.5.0
libsvg-cairo-0.5.0
libtiff-4.6.0
libwebp-1.3.2
libxml2-2.11.5
lua-5.4.6
lz4-1.9.4
mapcache-1.15dev
mapserver-git-main-2023-07-28
mod_fcgid-2.3.9
mod_h264_streaming-2.2.7
mod_wsgi-4.9.2
mrsid-9.5.4
mysql-8.0.26
nghttp2-1.54.0
netcdf-c-4.9.2
ogdi-git-master-2023-07-06
openssl-3.1.3
oracle-21.10.0.0.0
pcre-10.43-dev
pixman-0.42.2
php_ogr-1.6.0
poppler-23.09.0
postgresql-15.4
proj-9.3.0
protobuf-24.3
protobuf-c-1.4.1
Python-3.11.4
qhull-git-master-2023-05-22
readosm-1.1.0a
shapelib-git-master-2023-05-22
spatialite-tools-5.0.1
sqlite-3.43.1
swig-1.3.39
swigwin-3.0.12
szip-2.1.1
uriparser-0.9.7
xerces-c-3.2.4
zlib-1.2.13
zstd-1.5.5

OGR Formats Supported

See the OGR formats page for full driver descriptions.

Supported Formats:
  FITS -raster,vector- (rw+): Flexible Image Transport System
  PCIDSK -raster,vector- (rw+v): PCIDSK Database File
  netCDF -raster,multidimensional raster,vector- (rw+s): Network Common Data Format
  PDS4 -raster,vector- (rw+vs): NASA Planetary Data System 4
  VICAR -raster,vector- (rw+v): MIPL VICAR file
  PDF -raster,vector- (rw+vs): Geospatial PDF
  MBTiles -raster,vector- (rw+v): MBTiles
  BAG -raster,multidimensional raster,vector- (rw+v): Bathymetry Attributed Grid
  EEDA -vector- (ro): Earth Engine Data API
  OGCAPI -raster,vector- (rov): OGCAPI
  ESRI Shapefile -vector- (rw+v): ESRI Shapefile
  MapInfo File -vector- (rw+v): MapInfo File
  UK .NTF -vector- (rov): UK .NTF
  LVBAG -vector- (rov): Kadaster LV BAG Extract 2.0
  OGR_SDTS -vector- (rov): SDTS
  S57 -vector- (rw+v): IHO S-57 (ENC)
  DGN -vector- (rw+v): Microstation DGN
  OGR_VRT -vector- (rov): VRT - Virtual Datasource
  Memory -vector- (rw+): Memory
  CSV -vector- (rw+v): Comma Separated Value (.csv)
  NAS -vector- (rov): NAS - ALKIS
  GML -vector- (rw+v): Geography Markup Language (GML)
  GPX -vector- (rw+v): GPX
  LIBKML -vector- (rw+v): Keyhole Markup Language (LIBKML)
  KML -vector- (rw+v): Keyhole Markup Language (KML)
  GeoJSON -vector- (rw+v): GeoJSON
  GeoJSONSeq -vector- (rw+v): GeoJSON Sequence
  ESRIJSON -vector- (rov): ESRIJSON
  TopoJSON -vector- (rov): TopoJSON
  Interlis 1 -vector- (rw+v): Interlis 1
  Interlis 2 -vector- (rw+v): Interlis 2
  OGR_GMT -vector- (rw+v): GMT ASCII Vectors (.gmt)
  GPKG -raster,vector- (rw+vs): GeoPackage
  SQLite -vector- (rw+v): SQLite / Spatialite
  ODBC -vector- (ro):
  WAsP -vector- (rw+v): WAsP .map format
  PGeo -vector- (ro): ESRI Personal GeoDatabase
  MSSQLSpatial -vector- (rw+): Microsoft SQL Server Spatial Database
  OGR_OGDI -vector- (ro): OGDI Vectors (VPF, VMAP, DCW)
  PostgreSQL -vector- (rw+): PostgreSQL/PostGIS
  MySQL -vector- (rw+): MySQL
  OpenFileGDB -raster,vector- (rw+v): ESRI FileGDB
  DXF -vector- (rw+v): AutoCAD DXF
  FlatGeobuf -vector- (rw+v): FlatGeobuf
  Geoconcept -vector- (rw+v): Geoconcept
  GeoRSS -vector- (rw+v): GeoRSS
  VFK -vector- (ro): Czech Cadastral Exchange Data Format
  PGDUMP -vector- (w+v): PostgreSQL SQL dump
  OSM -vector- (rov): OpenStreetMap XML and PBF
  GPSBabel -vector- (rw+): GPSBabel
  OGR_PDS -vector- (rov): Planetary Data Systems TABLE
  WFS -vector- (rov): OGC WFS (Web Feature Service)
  OAPIF -vector- (ro): OGC API - Features
  EDIGEO -vector- (rov): French EDIGEO exchange format
  SVG -vector- (rov): Scalable Vector Graphics
  Idrisi -vector- (rov): Idrisi Vector (.vct)
  XLS -vector- (ro): MS Excel format
  ODS -vector- (rw+v): Open Document/ LibreOffice / OpenOffice Spreadsheet
  XLSX -vector- (rw+v): MS Office Open XML spreadsheet
  Elasticsearch -vector- (rw+): Elastic Search
  Carto -vector- (rw+): Carto
  AmigoCloud -vector- (rw+): AmigoCloud
  SXF -vector- (rov): Storage and eXchange Format
  Selafin -vector- (rw+v): Selafin
  JML -vector- (rw+v): OpenJUMP JML
  PLSCENES -raster,vector- (ro): Planet Labs Scenes API
  CSW -vector- (ro): OGC CSW (Catalog  Service for the Web)
  VDV -vector- (rw+v): VDV-451/VDV-452/INTREST Data Format
  GMLAS -vector- (rwv): Geography Markup Language (GML) driven by application schemas
  MVT -vector- (rw+v): Mapbox Vector Tiles
  NGW -raster,vector- (rw+s): NextGIS Web
  MapML -vector- (rw+v): MapML
  GTFS -vector- (rov): General Transit Feed Specification
  PMTiles -vector- (rw+v): ProtoMap Tiles
  JSONFG -vector- (rw+v): OGC Features and Geometries JSON
  TIGER -vector- (rov): U.S. Census TIGER/Line
  AVCBin -vector- (rov): Arc/Info Binary Coverage
  AVCE00 -vector- (rov): Arc/Info E00 (ASCII) Coverage
  HTTP -raster,vector- (ro): HTTP Fetching Wrapper

Oracle - see the GDAL Plugins section of this document to enable

"ro" means read-only
"rw" means read and one-time creation only
"rw+" means read, create and update
"w+" means write-only
"v" means that it supports virtual files

GDAL Formats Supported

See the GDAL formats page for full driver descriptions.

Supported Formats:
  VRT -raster,multidimensional raster- (rw+v): Virtual Raster
  DERIVED -raster- (ro): Derived datasets using VRT pixel functions
  GTiff -raster- (rw+vs): GeoTIFF
  COG -raster- (wv): Cloud optimized GeoTIFF generator
  NITF -raster- (rw+vs): National Imagery Transmission Format
  RPFTOC -raster- (rovs): Raster Product Format TOC format
  ECRGTOC -raster- (rovs): ECRG TOC format
  HFA -raster- (rw+v): Erdas Imagine Images (.img)
  SAR_CEOS -raster- (rov): CEOS SAR Image
  CEOS -raster- (rov): CEOS Image
  JAXAPALSAR -raster- (rov): JAXA PALSAR Product Reader (Level 1.1/1.5)
  GFF -raster- (rov): Ground-based SAR Applications Testbed File Format (.gff)
  ELAS -raster- (rw+v): ELAS
  ESRIC -raster- (rov): Esri Compact Cache
  AIG -raster- (rov): Arc/Info Binary Grid
  AAIGrid -raster- (rwv): Arc/Info ASCII Grid
  GRASSASCIIGrid -raster- (rov): GRASS ASCII Grid
  ISG -raster- (rov): International Service for the Geoid
  SDTS -raster- (rov): SDTS Raster
  DTED -raster- (rwv): DTED Elevation Raster
  PNG -raster- (rwv): Portable Network Graphics
  JPEG -raster- (rwv): JPEG JFIF
  MEM -raster,multidimensional raster- (rw+): In Memory Raster
  JDEM -raster- (rov): Japanese DEM (.mem)
  GIF -raster- (rwv): Graphics Interchange Format (.gif)
  BIGGIF -raster- (rov): Graphics Interchange Format (.gif)
  ESAT -raster- (rov): Envisat Image Format
  FITS -raster,vector- (rw+): Flexible Image Transport System
  BSB -raster- (rov): Maptech BSB Nautical Charts
  XPM -raster- (rwv): X11 PixMap Format
  BMP -raster- (rw+v): MS Windows Device Independent Bitmap
  DIMAP -raster- (rovs): SPOT DIMAP
  AirSAR -raster- (rov): AirSAR Polarimetric Image
  RS2 -raster- (rovs): RadarSat 2 XML Product
  SAFE -raster- (rov): Sentinel-1 SAR SAFE Product
  PCIDSK -raster,vector- (rw+v): PCIDSK Database File
  PCRaster -raster- (rw+): PCRaster Raster File
  ILWIS -raster- (rw+v): ILWIS Raster Map
  SGI -raster- (rw+v): SGI Image File Format 1.0
  SRTMHGT -raster- (rwv): SRTMHGT File Format
  Leveller -raster- (rw+v): Leveller heightfield
  Terragen -raster- (rw+v): Terragen heightfield
  netCDF -raster,multidimensional raster,vector- (rw+s): Network Common Data Format
  HDF4 -raster,multidimensional raster- (ros): Hierarchical Data Format Release 4
  HDF4Image -raster- (rw+): HDF4 Dataset
  ISIS3 -raster- (rw+v): USGS Astrogeology ISIS cube (Version 3)
  ISIS2 -raster- (rw+v): USGS Astrogeology ISIS cube (Version 2)
  PDS -raster- (rov): NASA Planetary Data System
  PDS4 -raster,vector- (rw+vs): NASA Planetary Data System 4
  VICAR -raster,vector- (rw+v): MIPL VICAR file
  TIL -raster- (rov): EarthWatch .TIL
  ERS -raster- (rw+v): ERMapper .ers Labelled
  L1B -raster- (rovs): NOAA Polar Orbiter Level 1b Data Set
  FIT -raster- (rwv): FIT Image
  GRIB -raster,multidimensional raster- (rwv): GRIdded Binary (.grb, .grb2)
  MrSID -raster- (rov): Multi-resolution Seamless Image Database (MrSID)
  JP2MrSID -raster- (rov): MrSID JPEG2000
  RMF -raster- (rw+v): Raster Matrix Format
  WCS -raster- (rovs): OGC Web Coverage Service
  WMS -raster- (rwvs): OGC Web Map Service
  MSGN -raster- (rov): EUMETSAT Archive native (.nat)
  RST -raster- (rw+v): Idrisi Raster A.1
  GSAG -raster- (rwv): Golden Software ASCII Grid (.grd)
  GSBG -raster- (rw+v): Golden Software Binary Grid (.grd)
  GS7BG -raster- (rw+v): Golden Software 7 Binary Grid (.grd)
  COSAR -raster- (rov): COSAR Annotated Binary Matrix (TerraSAR-X)
  TSX -raster- (rov): TerraSAR-X Product
  COASP -raster- (ro): DRDC COASP SAR Processor Raster
  R -raster- (rwv): R Object Data Store
  MAP -raster- (rov): OziExplorer .MAP
  KMLSUPEROVERLAY -raster- (rwv): Kml Super Overlay
  WEBP -raster- (rwv): WEBP
  PDF -raster,vector- (rw+vs): Geospatial PDF
  Rasterlite -raster- (rwvs): Rasterlite
  MBTiles -raster,vector- (rw+v): MBTiles
  PLMOSAIC -raster- (ro): Planet Labs Mosaics API
  CALS -raster- (rwv): CALS (Type 1)
  WMTS -raster- (rwv): OGC Web Map Tile Service
  SENTINEL2 -raster- (rovs): Sentinel 2
  MRF -raster- (rw+v): Meta Raster Format
  PNM -raster- (rw+v): Portable Pixmap Format (netpbm)
  DOQ1 -raster- (rov): USGS DOQ (Old Style)
  DOQ2 -raster- (rov): USGS DOQ (New Style)
  PAux -raster- (rw+v): PCI .aux Labelled
  MFF -raster- (rw+v): Vexcel MFF Raster
  MFF2 -raster- (rw+): Vexcel MFF2 (HKV) Raster
  GSC -raster- (rov): GSC Geogrid
  FAST -raster- (rov): EOSAT FAST Format
  BT -raster- (rw+v): VTP .bt (Binary Terrain) 1.3 Format
  LAN -raster- (rw+v): Erdas .LAN/.GIS
  CPG -raster- (rov): Convair PolGASP
  NDF -raster- (rov): NLAPS Data Format
  EIR -raster- (rov): Erdas Imagine Raw
  DIPEx -raster- (rov): DIPEx
  LCP -raster- (rwv): FARSITE v.4 Landscape File (.lcp)
  GTX -raster- (rw+v): NOAA Vertical Datum .GTX
  LOSLAS -raster- (rov): NADCON .los/.las Datum Grid Shift
  NTv2 -raster- (rw+vs): NTv2 Datum Grid Shift
  CTable2 -raster- (rw+v): CTable2 Datum Grid Shift
  ACE2 -raster- (rov): ACE2
  SNODAS -raster- (rov): Snow Data Assimilation System
  KRO -raster- (rw+v): KOLOR Raw
  ROI_PAC -raster- (rw+v): ROI_PAC raster
  RRASTER -raster- (rw+v): R Raster
  BYN -raster- (rw+v): Natural Resources Canada's Geoid
  NOAA_B -raster- (rov): NOAA GEOCON/NADCON5 .b format
  NSIDCbin -raster- (rov): NSIDC Sea Ice Concentrations binary (.bin)
  ARG -raster- (rwv): Azavea Raster Grid format
  RIK -raster- (rov): Swedish Grid RIK (.rik)
  USGSDEM -raster- (rwv): USGS Optional ASCII DEM (and CDED)
  GXF -raster- (rov): GeoSoft Grid Exchange Format
  KEA -raster- (rw+v): KEA Image Format (.kea)
  BAG -raster,multidimensional raster,vector- (rw+v): Bathymetry Attributed Grid
  HDF5 -raster,multidimensional raster- (rovs): Hierarchical Data Format Release 5
  HDF5Image -raster- (rov): HDF5 Dataset
  NWT_GRD -raster- (rw+v): Northwood Numeric Grid Format .grd/.tab
  NWT_GRC -raster- (rov): Northwood Classified Grid Format .grc/.tab
  ADRG -raster- (rw+vs): ARC Digitized Raster Graphics
  SRP -raster- (rovs): Standard Raster Product (ASRP/USRP)
  BLX -raster- (rwv): Magellan topo (.blx)
  PostGISRaster -raster- (rws): PostGIS Raster driver
  SAGA -raster- (rw+v): SAGA GIS Binary Grid (.sdat, .sg-grd-z)
  XYZ -raster- (rwv): ASCII Gridded XYZ
  HF2 -raster- (rwv): HF2/HFZ heightfield raster
  OZI -raster- (rov): OziExplorer Image File
  CTG -raster- (rov): USGS LULC Composite Theme Grid
  ZMap -raster- (rwv): ZMap Plus Grid
  NGSGEOID -raster- (rov): NOAA NGS Geoid Height Grids
  IRIS -raster- (rov): IRIS data (.PPI, .CAPPi etc)
  PRF -raster- (rov): Racurs PHOTOMOD PRF
  EEDAI -raster- (ros): Earth Engine Data API Image
  DAAS -raster- (ro): Airbus DS Intelligence Data As A Service driver
  SIGDEM -raster- (rwv): Scaled Integer Gridded DEM .sigdem
  TGA -raster- (rov): TGA/TARGA Image File Format
  OGCAPI -raster,vector- (rov): OGCAPI
  STACTA -raster- (rovs): Spatio-Temporal Asset Catalog Tiled Assets
  STACIT -raster- (rovs): Spatio-Temporal Asset Catalog Items
  GPKG -raster,vector- (rw+vs): GeoPackage
  OpenFileGDB -raster,vector- (rw+v): ESRI FileGDB
  PLSCENES -raster,vector- (ro): Planet Labs Scenes API
  NGW -raster,vector- (rw+s): NextGIS Web
  GenBin -raster- (rov): Generic Binary (.hdr Labelled)
  ENVI -raster- (rw+v): ENVI .hdr Labelled
  EHdr -raster- (rw+v): ESRI .hdr Labelled
  ISCE -raster- (rw+v): ISCE raster
  Zarr -raster,multidimensional raster- (rw+vs): Zarr
  HTTP -raster,vector- (ro): HTTP Fetching Wrapper

Directory Structure

• ms4w/

  • the main directory, assumed to be at the root of a drive, normally C:

• ms4w/Apache

  • the Apache installation

• ms4w/Apache/bin

  • the Apache binaries

• ms4w/Apache/cgi-bin

  • the location of mapserv.exe and its supporting libraries, and php.ini, php.exe.

• ms4w/Apache/cgi-bin/zooplugins

  • location of ZOO-Project files to enable additional support (see the ZOO-Project section of this document)

• ms4w/Apache/conf

  • the Apache configuration files. These should not be modified. Place all application-specific and local httpd.conf files in /ms4w/httpd.d (see the README.txt in that directory)

• ms4w/Apache/error

  • error files for Apache to use

• ms4w/Apache/htdocs

  • the Apache Web root directory, you shouldn't install much in here except perhaps for testing.

• ms4w/Apache/icons

  • icons used by Apache

• ms4w/Apache/include

  • include directory for compiling against Apache

• ms4w/Apache/lib

  • lib files for building against Apache

• ms4w/Apache/logs

  • log files for Apache are stored here, this should be archived or cleaned every so often.

• ms4w/Apache/manual

  • the Apache manual pages.

• ms4w/Apache/modules

  • modules for Apache (see the Apache Modules section of this document)

• ms4w/Apache/php

  • the PHP installation

• ms4w/Apache/php/ext

  • location of phpmapscript dll

• ms4w/apps

  • put all applications in subdirectories here.

• ms4w/apps/etc

  • sample fonts and symbols for use in MapServer mapfiles

• ms4w/gdalbindings

  • contain GDAL bindings for CSharp, Java, and Python (see the GDAL Bindings section of this document)

• ms4w/gdaldata

  • supporting files for GDAL data formats

• ms4w/gdalplugins

  • move dlls to this folder that are required for GDAL plugins e.g. 'oci_OCI.dll' (see the GDAL Plugins section of this document)

• ms4w/httpd.d

  • put all application-specific and local httpd.conf files here (see the README.txt in that directory)

• ms4w/msplugins

  • location of the plugin dlls for MapServer (see the MapServer Plugins section of this document)

• ms4w/msplugins/mapscript

  • location of CSharp, Java, and Python mapscript files (see the MapScript configuration section of this document)

• ms4w/Python

  • an embedded installation of Python
  • must execute setenv.bat before use

• ms4w/share

  • an installation of PROJ (formerly referred to as "PROJ.4")

    • EPSG projections are stored in the proj.db SQLite database
    • grid files will be stored in this proj folder

  • location of OGCAPI template files
  • osm2pgsql style files

• ms4w/tmp

  • temporary files go here. This should be cleaned regularly

• ms4w/tmp/ms_tmp

  • temporary files that need to be Web-accessible go here (i.e. image files created by mapserver). This is available as /ms_tmp/ via URL. Normally this means that your MAP files would have an IMAGEPATH of /ms4w/tmp/ms_tmp/ and a IMAGEURL of /ms_tmp/

• ms4w/tools

  • contains useful tools such as the gdal/ogr utilities and mapserv utilities (note that before running these you must execute the /ms4w/setenv.bat script in your command window)

Upgrading from an older version of MS4W

If you already have MS4W installed please do the following:

• open a DOS command window and execute the file '/ms4w/apache-uninstall.bat' at the commandline. This file will stop and uninstall your Apache service. You should see the following message flash in the command window:

The "Apache MS4W Web Server" service is stopping.
The "Apache MS4W Web Server" service has stopped.

Removing the "Apache MS4W Web Server" service
The "Apache MS4W Web Server" service has been removed
successfully.

• your old apache service has now been removed
• make sure no files or other services point the your ms4w folder. If your browser is currently open and you are a viewing an ms4w page you will not be able to rename the ms4w folder. Therefore you must close all ms4w documents, all ms4w browser windows...make sure no running files point to the ms4w folder.
• rename the old ms4w folder to something like 'ms4w-old'
• extract the ms4w_xx.zip file to the root of a drive on your machine
• if successful, you should have a new directory named 'ms4w' at the root of the drive you chose (e.g. C:/ms4w or D:/ms4w ).
• follow the rest of the install instructions in /ms4w/README_INSTALL.txt to start apache...

Extracting MS4W for the first time

Please read through the following instructions before starting your installation.

1. To install the MS4W .zip file, use a compression program (e.g. 7zip) to extract the package at the root of a drive, e.g., drive C:/. If successful, you should have a new directory named 'ms4w' at the root of the drive you chose (e.g. C:/ms4w).

   Warning

   If you are using the setup.exe installer: Some applications may have a problem if you install MS4W in a path containing spaces. It is therefore not recommended to install MS4W in a path that contains spaces. It is always best to install MS4W at the root of a drive, such as C:/ or D:/

2. Be sure to follow the instructions in the local file /ms4w/REQUIREMENTS.txt to install the C++ Redistributable on your system before proceeding.

3. Start your MS4W Apache Web Server by running /ms4w/apache-install.bat (open a Command Prompt window and execute it at the command line - it is not recommended to just double-click the file). This file installs Apache as a Windows service (called "Apache Web Server") so that it starts whenever your machine is restarted. When executed, the following message should be displayed in the command window:

   Installing the Apache MS4W Web Server service
   The Apache MS4W Web Server service is successfully installed.
   Testing httpd.conf....
   Errors reported here must be corrected before the service
   can be started.
   The Apache MS4W Web Server service is starting.
   The Apache MS4W Web Server service was started successfully.
   

   This means that Apache is running and installed as a service.

   Note for Windows 11, 10, 8, 7 and Vista Users:

   In order to run the apache-install.bat file, you must do the following:

   1. In Windows Explorer, goto the location of your cmd.exe file (C:/Windows/System32)
   2. Right-click the cmd.exe executable and choose Run as Administrator
   3. Navigate to your ms4w folder in the command prompt window and run apache-install.bat

4. To test that Apache is running properly, open your Web browser and find your local host Web service by entering one of the following URLs:

   http://localhost/
   
   or
   
   http://127.0.0.1/
   

   You should now see the main MS4W page in your Web browser. This gives you general information about your install along with configuration information. If this is your first time using MS4W it is very important that you review the listed "Features" installed within MS4W, and test them by selecting each link found on this page.

5. Technically, at this point, MS4W is installed! However, as you may have noticed from the MS4W main index.html page, there are no applications running. What this means is that there are no Web applications like GeoMoose or OpenLayers found within MS4W's Web-accessible directory, /ms4w/apps/. The MS4W-configured Web applications can be found on https://ms4w.com/release/apps/ as separate zip files.

6. To install these Web application into /ms4w/apps/ all that is required is to unzip the Web application compressed file at the same root directory as MS4W (e.g., C:/).

   Two things should happen when uncompressing this file. First, the Web application directory should appear within /ms4w/apps/. Second, a new httpd_*.conf file should be added to /ms4w/httpd.d/httpd_*.conf. (The /httpd.d/ directory contains Apache configuration files that define which files on your computer/server are Web-accessible. For each Web application that you install, a new configuration file will be found.)

7. The definitions of these Web-accessible directories are called Web Aliases. In order to activate a Web Alias you must restart Apache. To test your latest installed application, go to the MS4W main index.html page (i.e., http://localhost/). In the applications section you should now find a link to the application you just installed. Select the link to the recently installed application to see if it is configured correctly. Another option is to find the Web Alias for your application and call it from your Web browser directly. For example, if you have installed the latest MS4W version of GeoMoose, the Web Alias is "geomoose2". To go to the GeoMoose index page, simply enter http://localhost/geomoose2/.

   Note: Applications with configuration files (e.g., GeoMoose and OpenLayers) generally do not require any editing of their files in order to work. Just unzip to the appropriate driver root and restart Apache.

   WARNING: It is very possible that you may wish (but not encouraged!) to run multiple versions of the same product. For example, GeoMoose 2.8.0 vs. GeoMoose 2.8.1. When installing these ms4w GeoMoose application packages, you will notice when unzipping GeoMoose that the httpd_geomoose2_ms4w.conf file found under ./ms4w/httpd.d/ will be overwritten by the GeoMoose you are currently installing. The reason for this is that the GeoMoose Alias stays the same from version to new version of GeoMoose. So, if you overwrite the httpd_geomoose2_ms4w.conf when unzipping and then restart Apache, you will get the latest version of GeoMoose that you just installed. To run both GeoMoose versions simply follow the instructions in Step 7.

8. You also can create new Web Alias(es). To configure your own personal Web Alias(es), follow the instructions in /ms4w/httpd.d/README_HTTPD.txt

MapServer Plugins

MapScript configuration

MS4W >= 1.5.0 includes pre-built support files for CSharp, Java, PHP, and Python mapscript. In order to make use of these, however, they must be installed and configured in the appropriate locations on your system.

mapserv, GDAL, Python, PHP, and commandline MS4W tools path set

Python 3.11.4

python -m pip install --upgrade pip

python -m pip install Sphinx==7.0.1

#!C:\ms4w\Python\python.exe -u

ScriptInterpreterSource Registry

SetEnv PYTHONUNBUFFERED 1
PassEnv PYTHONPATH

GDAL Plugins

GDAL Bindings

MS4W contains GDAL bindings for CSharp, Java, and Python, and are located at /ms4w/gdalbindings

PROJ Networking

Since MS4W 5.0, the included projections library PROJ allows leveraging associated grid files for increased accuracy. These grid files can be loaded on-demand, however this is not recommended for online mapping; instead MS4W contains a script to execute to download all grid files, before you begin mapping:

1. Open a Command Prompt window
2. cd ms4w
3. setenv.bat
4. execute: proj-install-grids.bat
5. the grids will be stored in the folder /ms4w/share/proj/
6. For more PROJ network settings, see the included proj.ini file at /ms4w/share/proj/ and the related documentation: https://proj.org/usage/network.html

FastCGI

In order to use FastCGI you must do the following:

1. Open /ms4w/Apache/conf/httpd.conf in a text editor

2. Uncomment line#178, such as:

   LoadModule fcgid_module modules/mod_fcgid.so
   

3. At the bottom of the file you will see a commented "<IfModule fcgid_module>" section. If you want to use FastCGI directives (listed on the mod_fcgid page) you can uncomment the section and add your directives, such as:

   <IfModule fcgid_module>
      FcgidMinProcessesPerClass 0
      FcgidIdleScanInterval 1
      FcgidProcessLifeTime 10
   </IfModule>
   

4. If you are connecting to an Oracle database using FastCGI, you must also add your Oracle Bin directory (where the 'oci.dll' file exists) to the PATH variable above, such as:

   <IfModule fcgid_module>
       ...
       FcgidInitialEnv PATH "c:/oracle/product/10.2.0/client/BIN"
       ...
   </IfModule>
   

5. Save the file and restart apache (execute /ms4w/apache-restart.bat)

6. Change your CGI application to point to "/fcgi-bin/mapserv.exe" instead of the usual "/cgi-bin/mapserv.exe"

7. Add the following parameter to your layer for which you want this FastCGI connection:

   PROCESSING "CLOSE_CONNECTION=DEFER"
   

8. Try the application. If successful you should see the "mapserv.exe" process in the Windows Task Manager remain open while the user interacts with your application.

Notes:

• in testing this was successful with PostgreSQL 9.0.4 / PostGIS 1.5.2, and with Oracle 10.2.0.1.0.
• general MapServer and FastCGI notes can be found in the FastCGI Howto.

Apache Modules

TinyOWS

TinyOWS and demo data are included (as of MS4W 3.1.0), giving you full WFS-Transaction support (making data changes in an MS4W map that is then saved to the underlying database). In order to use TinyOWS you must do the following:

1. Make sure that you have PostgreSQL and PostGIS installed locally, or have connection details for accessing it remotely. This has been tested with PostgreSQL 15.3 and PostGIS 3.3.3

2. First we must create a database and load some sample data:

   • Open /ms4w/apps/tinyows/demo/install-demo-data.bat in a text editor

   • If necessary, modify the PG-PORT, PG-SUPERUSER-NAME, and PG-SUPERUSER-PASSWORD for your installation (lines ~16-20). Save your changes.

   • Open a Command prompt window, and cd into /ms4w/ and execute setenv.bat

   • cd into /ms4w/apps/tinyows/demo/ and execute the following in that same window:

     install-demo-data.bat
     

   • Verify that a new database was created ("tinyows"), and that there is a spatial table ("frida").

3. Next we must configure TinyOWS:

   • Open /ms4w/apps/tinyows/config.xml in a text editor

   • If necessary, modify the online_resource and pg connection parameters, for your installation. Refer to the TinyOWS documentation for parameter descriptions. Save your changes.

   • to test this configuration, in the same Command prompt window, execute the following (change the drive path if necessary):

     set TINYOWS_CONFIG_FILE=C:/ms4w/apps/tinyows/config.xml
     

   • once that is set, execute the following in the same Command prompt window to see details about your TinyOWS configuration:

     tinyows.exe --check
     

     the response should be something like:

     TinyOWS version:   1.2.0
     FCGI support:      Yes
     Config File Path:  C:/ms4w/apps/tinyows/config.xml (TinyOWS XML)
     PostGIS Version:   3.3.3
     PostGIS dsn:       host=localhost user=postgres password=postgres dbname=tinyows port=5432
     Output Encoding:   UTF-8
     Database Encoding: UTF8
     Schema dir:        /ms4w/apps/tinyows/schema/
     Display bbox:      Yes
     Estimated extent:  No
     Check schema:      No
     Check valid geoms: Yes
     Available layers:
     
       public.frida (31467) -> tows:frida [RW]
     

   • Note that Apache sets this same environment variable TINYOWS_CONFIG_FILE in the file /ms4w/httpd.d/httpd_tinyows.conf

4. Next we should configure the demo HTML application:

   • Open /ms4w/apps/tinyows/demo/tinyows.js in a text editor
   • Verify that urls (such as http://127.0.0.1) used there are correct: see lines 65 & 69

5. Finally we are ready to test a WFS-T transaction to your database:

   • in a Web browser, goto http://127.0.0.1/tinyows/demo/tinyows.html (or modify that address if need be)

   • click on the "Draw Feature" icon on the top-right of the map, and click anywhere on the map to generate a polygon (to close the polygon double-click).

   • now click on the "Save Changes" icon, you should see a message in the right panel of that page as:

     Transaction successfully completed
     

   • Changes to the "frida" layer should be saved to the database.

     Tip

     If you have the PostGIS layer already loaded in QGIS, if you pan the map, you should see your new feature displayed.

pycsw

pycsw catalogue server is included in the base MS4W installer, as of the MS4W 4.0 release, giving you a lightweight metadata publisher, that runs through MS4W's embedded Python instance. Through pycsw you can not only serve your metadata catalogue, but also harvest other remote OGC services (WMS, WFS, WCS, WPS, etc.), as well as remotely edit your metadata repository (through CSW-T transactions). Here are some important notes on this pycsw instance:

1. pycsw runs through the mod_wsgi Apache Module (see around line#646 of the file /ms4w/Apache/conf/httpd.conf). Please see that section for mod_wsgi configure instructions.

2. pycsw can alternatively be configured to run through CGI, instead of through mod_wsgi:

   • comment the mod_wsgi section around line#652 of the file /ms4w/Apache/conf/httpd.conf as:

     # run pycsw through mod_wsgi
     # WSGIApplicationGroup %{GLOBAL}
     # WSGIScriptAlias /pycsw "/ms4w/apps/pycsw-xxx/pycsw/wsgi.py"
     # SetEnvIf Request_URI "/pycsw$" "PYCSW_CONFIG=/ms4w/apps/pycsw-xxx/default.cfg"
     # <Directory "/ms4w/apps/pycsw-xxx/pycsw">
       # Order deny,allow
       # Allow from all
     # </Directory>
     

   • uncomment the CGI section around line#661 of the file /ms4w/Apache/conf/httpd.conf as:

     # run pycsw as CGI
     ScriptAlias /pycsw "/ms4w/apps/pycsw-xxx/csw.py"
     SetEnvIf Request_URI "/pycsw$" "PYCSW_CONFIG=/ms4w/apps/pycsw-xxx/default.cfg"
     <Directory "/ms4w/apps/pycsw-xxx">
       Options +FollowSymLinks +ExecCGI
       Allow from all
       AddHandler cgi-script .py
     </Directory>
     

   • restart the Apache service (execute /ms4w/apache-restart.bat)

3. You can configure this sample service, in the file "default.cfg", and you can find the path to it on line#655 of the file: /ms4w/Apache/conf/httpd.conf (look for the "PYCSW_CONFIG" setting there). For definitions of the parameters see pycsw's configuration guide.

4. You must restart the Apache service after each change to that .cfg file. (execute /ms4w/apache-restart.bat)

5. A sample CSW service is pre-configured for you, and the GetCapabilities request is: http://127.0.0.1/pycsw?service=CSW&version=3.0.0&request=GetCapabilities

6. To use the "pycsw-admin.py" utility:

   • open a Command window
   • cd ms4w
   • setenv.bat
   • pycsw-admin.py -h

   For usage parameters of the admin utility see pycsw's administration guide.

ZOO-Project

ZOO-Project Web Processing Server is included as an add-on package, as of the MS4W 4.0 release, giving you a full WPS server, that runs through MS4W's Apache instance. Here are some important notes on this ZOO-Project WPS instance and its many compiled services:

1. Please see your local MS4W homepage (http://127.0.0.1) for a working list of GetCapabilities, DescribeProcess, and Execute requests for the various WPS services.

Important

Since 2020-01-30 a local demo is included, leveraging ZOO-Project's vector-based spatial analysis, through OGR services. You can find the demo linked on your local MS4W homepage (as "local OGR Services demo").

2. The following support has been compiled into the ZOO-Project kernel, as part of MS4W:

   • MapServer support (official docs)
   • PHP support (official docs)
   • Python support (official docs)
   • C# Mono support (official docs) see note below to enable
   • Java support (official docs) see note below to enable
   • GDAL and OGR support (official docs)
   • Status service support (official docs)

3. The ZOO kernel configuration file main.cfg can be found in /ms4w/Apache/cgi-bin/ . For definitions of the parameters see the configuration guide.

4. Individual ZOO service configuration files (.zcfg) can also be found in /ms4w/Apache/cgi-bin/ . For definitions of the parameters see the services configuration guide.

5. To enable C# Mono support you are required to do the following:

   • move the zoo_loader.cgi plugin file up from /ms4w/Apache/cgi-bin/zooplugins/mono/ into /ms4w/Apache/cgi-bin/

   • add the following to your main.cfg file, pointing to your local installation of Mono:

     [mono]
     lib=C:\Program Files (x86)\Mono\lib
     etc=C:\Program Files (x86)\Mono\etc
     

6. To enable Java support you are required to do the following:

   • move the zoo_loader.cgi plugin file up from /ms4w/Apache/cgi-bin/zooplugins/java/ into /ms4w/Apache/cgi-bin/

   • add the following to your main.cfg file, pointing to your local installation of JDK:

     [java]
     java.library.path=C:\Program Files (x86)\Java\jdk1.8.0_77\jre\bin\client HelloJava.class
     

   • You may have to move your local jvm.dll file into /ms4w/Apache/cgi-bin/ as well

Certificates for HTTPS

As of MapServer 5.4.1, MapServer can connect through HTTPS connections to WMS/WFS servers. MS4W 3.0 (and newer) includes the necessary configuration as follows:

1. Certificate authority bundle is included in /ms4w/Apache/conf/ca-bundle/cacert.pem

   Source: http://curl.haxx.se/ca/cacert.pem

2. Apache's httpd.conf points to the ca-bundle:

   SetEnv CURL_CA_BUNDLE "/ms4w/Apache/conf/ca-bundle/cacert.pem"
   

"D:/ms4w/Apache/conf/ca-bundle/cacert.pem"

  or

"C:/ms4w/Apache/conf/ca-bundle/cacert.pem"

3. MS4W's setenv.bat points to the ca-bundle:

   set CURL_CA_BUNDLE=\ms4w\Apache\conf\ca-bundle\cacert.pem
   set SSL_CERT_FILE=\ms4w\Apache\conf\ca-bundle\cacert.pem
   set OPENSSL_CONF=\ms4w\tools\openssl\openssl.cnf
   

4. MS4W's php.ini points to the ca-bundle:

   curl.cainfo="/ms4w/Apache/conf/ca-bundle/cacert.pem"
   openssl.cafile="/ms4w/Apache/conf/ca-bundle/cacert.pem"
   

5. For more information on SSL certificates, see: http://curl.haxx.se/docs/sslcerts.html

6. To setup MapServer as a client to access a remote WMS/WFS server through HTTPS see: https://mapserver.org/ogc/wxs_secure.html

7. To enable HTTPS for your server host (to serve its own certificate, for your domain such as https://mydomain.com), you can use "win-acme" at https://www.win-acme.com/ Here are some important tips specifically related to win-acme:

   • follow the steps for Apache at https://www.win-acme.com/manual/advanced-use/examples/apache

   • be sure to set the SavePrivateKeyPem option in win-acme's settings.config to True

   • edit your httpd.conf and around line#176 be sure to uncomment the line:

     LoadModule ssl_module modules/mod_ssl.so
     

   • change the ServerName parameter in httpd.conf around line#226 to your domain such as:

     ServerName mydomain.com
     

   • add the following to the bottom of your httpd.conf (edit the paths to your generated certificate files):

     <IfModule mod_ssl.c>
         Listen 443
     </IfModule>
     
     <VirtualHost *:443>
         DocumentRoot "/ms4w/Apache/htdocs"
         ServerName mydomain.com
         ErrorLog "logs/https_error_log.txt"
         CustomLog "logs/https_error_access.txt" common
         SSLEngine on
         SSLCertificateFile "C:/ProgramData/win-acme/acme-v02.api.letsencrypt.org/Certificates/ca-umz9yz4SYUGQm-esziIA9A-chain.pem"
         SSLCertificateKeyFile "C:/ProgramData/win-acme/acme-v02.api.letsencrypt.org/Certificates/umz9yz4SYUGQm-esziIA9A-key.pem"
     </VirtualHost>
     

   • restart Apache (execute /ms4w/apache-restart.bat)

   • use a tool to verify your certificate such as https://www.ssllabs.com/ssltest/

Troubleshooting

Warning: dl(): Unable to load dynamic library '/ms4w/Apache/php/ext/php_mapscript.dll'

1. Verify that the dll in question exists in the specified location (/ms4w/Apache/php/ext/).

2. This php_mapscript dll requires several other dlls, and the problem may be that one is missing on your system. In order to hopefully get more information on what dll is missing, go to a command prompt, and do the following:

   cd ms4w
   setenv.bat
   cd Apache/htdocs
   php -dextension=C:/ms4w/Apache/php/ext/php_mapscript.dll quickmap.php
   

   A windows error window should open with a message like:

   The dynamic link library ***** could not be found in
   the specified path...
   

   Locate this missing dll and copy it either to /ms4w/Apache/cgi-bin/ or your system32 folder.

3. If you are still unsure what dll is causing this unable to load dynamic library error, a useful utility to find what associated dlls are missing on your system is Dependency Walker. Download the utility, execute the exe, and open your php_mapscript dll.

The Program can't start because MSVCRxxx.dll is missing from your computer

Please follow the instructions included locally inside the document /ms4w/REQUIREMENTS.txt to install the C++ Redistributable.

Clicking on apache-install.bat flashes a DOS window and does not install the service

To see the exact error message, open a Command window, and execute the 'apache-install.bat' file from a DOS prompt.

cd ms4w

apache-install.bat

Only one usage of each socket address (protocol/network address/port) is normally permitted. : make_sock: could not bind to address 0.0.0.0:80 no listening sockets available, shutting down

Apache with MS4W is configured to use port 80. Your system might be already using this port (IIS could cause this for example). If you want to change the port that Apache uses modify the following file:

/ms4w/Apache/conf/httpd.conf

line 120: Listen 80

TCPView is an example of shareware that lets you see how the ports on your machine are being used.

The procedure entry point xxxx could not be located in the dynamic link library xxx.dll

Make sure that MapServer (or the utility that you are trying to use) is actually using the 'xxx.dll' file that is part of the MS4W package. You could be experiencing 'dll hell' (http://en.wikipedia.org/wiki/DLL_hell) where MS4W is actually finding an older dll on your system. Try renaming the other dll(s) of the same name, keeping the one in MS4W as is, and retrying your application/command.

Other Problems...

1. Search the mailing list archives to see if someone has encountered/solved your same issue.

2. If your issue has not been brought up on the mailing list and dealt with, submit a question to the MS4W mailing list. Include the steps to reproduce your problem, and state your exact error message. Also specify which version of MS4W you are using.

Modifying MS4W for an Installation not at the Drive Root

Do the following steps in a text editor:

1. Open /ms4w/Apache/conf/httpd.conf and search for "/ms4w/" and replace with your new path from your drive root (such as "/Temp/ms4w/")
2. Open /ms4w/Apache/cgi-bin/php.ini and search for "/ms4w/" and replace with your new path from your drive root (such as "/Temp/ms4w/")
3. Open all files in /ms4w/httpd.d and search for "/ms4w/" and replace with your new path from your drive root (such as "/Temp/ms4w/")
4. Open /ms4w/setenv.bat and search for "/ms4w/" and replace with your new path from your drive root (such as "/Temp/ms4w/")
5. Configure your add-on packages, typically installed at /ms4w/apps/

Recommendation: avoid installing MS4W in a path that contains spaces

Installing the MS4W MapServer Binaries in Other Environments

The following instructions will help non-MS4W users who want to only use the MapServer binaries included in MS4W:

1. Download and extract the MS4W base package locally from ms4w.com
2. Do not install the Apache service (apache-install.bat)
3. Copy the .dll files from the /ms4w/apache/cgi-bin/ directory into your desired cgi-bin directory:
4. For PHP/Mapscript, goto /ms4w/Apache/php/ext/ and copy the php_mapscript.dll file into your own PHP extensions directory. CSharp, Java, and Python mapscript files can be found in /ms4w/msplugins/mapscript/
5. For the commandline utilities that come with MS4W (mapserv, gdal, etc.) copy all of the .exe files from /ms4w/tools/ to a desired location, but be aware that these utilities use dlls that were installed in the cgi-bin directory. Therefore you must add your cgi-bin directory into your Windows PATH environment variable before running the utilities.
6. Microsoft IIS users should refer to the IIS Howto for MapServer.

Using Custom EPSG Projections

Custom EPSG projections can be added to the bottom of your epsg file at /ms4w/proj/nad/epsg/.

As of MS4W 3.0-beta11, previously included custom projections for Canada have been removed. Here is some of the history:

• GatewayGeo officially applied to have the custom Canadian projection EPSG:42304 (common in Ontario and in the Atlas of Canada) included in the EPSG geodetic registry in 2009
• the projection was accepted as EPSG:3978 in the EPSG geodetic registry on 2009-06-02
• this new EPSG code is included in PROJ 4.7.0 release (2009-09)

For reference, here are the old custom Canadian EPSG codes:

##
## Custom projection codes for Canada
##
## WGS84 / LCC Canada
<42101> +proj=lcc +ellps=WGS84 +lat_0=0 +lon_0=-95 +lat_1=49
        +lat_2=77 +x_0=0 +y_0=-8000000.0 +datum=WGS84
        +units=m no_defs <>
## NAD83 / BC Albers
<42102> +proj=aea +ellps=GRS80 +lat_0=45 +lon_0=-126.0
        +lat_1=50.0
        +lat_2=58.5 +x_0=1000000.0 +y_0=0 +datum=NAD83
        +units=m no_defs <>
#
## NAD83 LCC for Canada
<42304> +proj=lcc +ellps=GRS80 +lat_0=49 +lon_0=-95
        +lat_1=49 +lat_2=77
        +datum=NAD83 +units=m no_defs <>
##

Security Steps to Enable

1. (Required) Configure the file /ms4w/ms4w.conf

2. (Strongly Recommended) Set MS_MAP_PATTERN in your local Apache httpd.conf file, to disallow common malicious manipulation of the MAP= parameter:

   1. open in your favorite text editor the file /ms4w/Apache/conf/httpd.conf and add the following line to the bottom of the file:

      SetEnv MS_MAP_PATTERN "^(C:)?\/ms4w\/apps\/((?!\.{2})[_A-Za-z0-9\-\.]+\/{1})*([_A-Za-z0-9\-\.]+\.(map))$"
      

      The above regular expression will limit paths to the common C:/ms4w/apps/ directory (where all MS4W mapfiles and applications live), allow encoded urls, allow "." or "_" or "-" in MAP= paths but disallow ".." directory traversing.

   2. restart the Apache MS4W Web Server service

   Tip

   You can build and test your regular expression with the online tool RegExr. Follow these steps to test there:

   1. Click on "Javascript" in the top-right and select "PCRE" (which is the actual regex library used by MS4W).

   2. Click on "Flags" in the top-right and click to disable "global" and disable any other that are enabled.

   3. In the "Expression" panel at the top, paste your draft regular expression:

      SetEnv MS_MAP_PATTERN "^(C:)?\/ms4w\/apps\/((?!\.{2})[_A-Za-z0-9\-\.]+\/{1})*([_A-Za-z0-9\-\.]+\.(map))$"
      

   4. Move your mouse over parts of the expression, and a helpful popup will appear explaining what that section is (in regular expression language, which helps you learn the terms and/or search for more specific help online). For example, below you can see that I clicked inside the first character set: [_A-Za-z0-9-.] that specifies what characters (including numbers, underscore, dash, or period) are allowed in the path:

      

   5. Now begin to add tests, by clicking on the "Tests" button below the expression, and click the "Add Test" link. Here, paste in your first test, which can be one that must work/be valid, such as C:/ms4w/apps/ogc-demos/demo.map. You can even give it a name "Valid path". A green checkmark should instantly appear, telling you that the path is valid, according to your expression.

      

   6. Add a test for malicious directory traversing, as: ../../../Users/All/Users/Microsoft/Settings/xxx.map Your result there should give a red X, showing that this is not allowed with your expression.

      

   7. Add a test for a malicious filetype, as: xxx.js Your result there should give a red X, showing that this is not allowed with your expression.

      

   8. Repeat after me, say this out loud 10 times:

      Regular expressions are fun, I love regex.
      Regular expressions are fun, I love regex.
      Regular expressions are fun, I love regex.
      Regular expressions are fun, I love regex.
      Regular expressions are fun, I love regex.
      Regular expressions are fun, I love regex.
      Regular expressions are fun, I love regex.
      Regular expressions are fun, I love regex.
      Regular expressions are fun, I love regex.
      Regular expressions are fun, I love regex.
      

   9. Sleep easily as you have helped secure your MS4W server.

   The above MS_MAP_PATTERN expression has now been implemented on the MS4W official demo server. MS4W is installed there on the default (and recommended) path of C:/ms4w/, and all applications and mapfiles live in the recommended C:/ms4w/apps/ sub-directories. You can now try yourself some example tests against that server, with that secure MS_MAP_PATTERN set through Apache:

   • regular CGI request with MAP= (this is how it looks for all MS4W users out-of-the-box): https://ms4w.dev/cgi-bin/mapserv.exe?MAP=/ms4w/apps/local-demo/local.map&MODE=browse&TEMPLATE=openlayers&LAYERS=all
   • with the correct drive specified in MAP= request : https://ms4w.dev/cgi-bin/mapserv.exe?MAP=C:/ms4w/apps/local-demo/local.map&MODE=browse&TEMPLATE=openlayers&LAYERS=all
   • with a malicious MAP=C:/Users/All Users/Microsoft/Settings/xxx.js path (notice the result is: "Parameter 'map' value fails to validate") : https://ms4w.dev/cgi-bin/mapserv.exe?MAP=C:/Users/All%20Users/Microsoft/Settings/xxx.js&MODE=browse&TEMPLATE=openlayers&LAYERS=all
   • with an incorrect drive (D) that is not allowed by the expression (notice the result is: "Parameter 'map' value fails to validate") : https://ms4w.dev/cgi-bin/mapserv.exe?map=D:/ms4w/apps/local-demo/local.map&MODE=browse&TEMPLATE=openlayers&LAYERS=all
   • attempting directory traverse (notice the result is: "Parameter 'map' value fails to validate") : https://ms4w.dev/cgi-bin/mapserv.exe?map=../../../Users/All%20Users/Microsoft/Settings/xxx.map&MODE=browse&TEMPLATE=openlayers&LAYERS=all

   Note

   Future MS4W releases (as well as MapServer releases) will likely contain a default MS_MAP_PATTERN enabled.

3. (Recommended) Set MS_MAPFILE through Apache, to hide the MAP= path from MapServer requests, on your public MapServer services.

4. (Optional) Set MS_MAP_NO_PATH through Apache, to forbid all MAP= requests in your visible MapServer calls.

Copyright/Licensing Information

In general MS4W is licensed under an MIT/X style license with the following terms:

Copyright (c) 2003-2023 GatewayGeo

Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"),to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

Component Licensing

MS4W contains several component packages that are provided under their own licensing terms.