Changes between Version 9 and Version 10 of MapServerErrors


Ignore:
Timestamp:
Jan 27, 2009, 1:11:05 PM (15 years ago)
Author:
jmckenna
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • MapServerErrors

    v9 v10  
    3232    * The !DocumentRoot in the web server could be changed.
    3333      * (is there a single file in which to define !MapServer's root?)
    34 
    3534          Information about file placement is in http://www.mapserver.org/utilities/manage.html
    36 
    37                 + (How to find out where an installation of mapserv is trying to access files? Particularly if access fails.)
    38 
     35      * (How to find out where an installation of mapserv is trying to access files? Particularly if access fails.)
    3936          Assuming /var/www/html is the web server's document root, the location of /data might actually be:
    40 {{{
    41                 + /var/www/cgi-bin/data
    42                 + /var/www/htdocs/data
    43                 + /var/www/html/data
    44                 + /var/www/data
    45                 + /data
    46                       # (If the !MapServer Tutorial is referring to /data, what can be changed to have !MapServer find data elsewhere?)
    47 }}}
     37        * /var/www/cgi-bin/data
     38        * /var/www/htdocs/data
     39        * /var/www/html/data
     40        * /var/www/data
     41        * /data
     42          * (If the !MapServer Tutorial is referring to /data, what can be changed to have !MapServer find data elsewhere?)
    4843=== 500 Internal Server Error ===
    49           o The server encountered an internal error or misconfiguration and was unable to complete your request.
     44  * The server encountered an internal error or misconfiguration and was unable to complete your request.
    5045
    5146    Something went wrong.
    5247
    53           o The people in charge of the !MapServer installation will have to figure out the problem.
    54           o If running from a console cgi-bin/mapserv -v reports both INPUT=GDAL and INPUT=TIFF there may be a conflict due to including TIFF as well as GDAL. http://lists.gis.umn.edu/pipermail/mapserver-users/2004-March/011072.html
     48  * The people in charge of the !MapServer installation will have to figure out the problem.
     49  * If running from a console cgi-bin/mapserv -v reports both INPUT=GDAL and INPUT=TIFF there may be a conflict due to including TIFF as well as GDAL. http://lists.gis.umn.edu/pipermail/mapserver-users/2004-March/011072.html
    5550
    5651          o See also Premature end of script headers...