Wiki Testing/ServerInstallationGuideFootnotes

From OPeNDAP Documentation
Revision as of 08:22, 3 January 2008 by Yuan (talk | contribs)
⧼opendap2-jumptonavigation⧽

References

  1. http://spg.gsfc.nasa.gov/rfc/004
  2. The actual directory name, or whether the CGI programs are kept in a particular directory (or named with a particular convention) is another detail of the specific web server and configuration used. The web server might refer to the directory as the ScriptAlias directory, as it does with Apache.
  3. When you fill out some HTML form, you are usually sending data in a "POST" request. When you type a URL into your web browser, this is a "GET" request. HTTP servers can respond to both kinds of request.
  4. This is not shown in this illustration, but it would follow a question mark in the URL, like this: http://test.opendap.org/opendap/nph-dods/temp.nc.asc?temp[0:180][0:45]. For more information about constraint expressions, see The DODS Quick Start Guide or The OPeNDAP User Guide.
  5. A user has contributed examples for this. Go to http://seawater.tamu.edu/noppdodsgom and click on "Resources."
  6. The user is yet another configurable feature. For the Apache server, you can look for a line in the configuration file specifying the user, using the keyword User. On my machine, where httpd runs as nobody, it looks like this: User nobody.
  7. ...also tested on Apache 2.0.40, 07/25/03 jhrg
  8. Brock Murch <bmurch@marine.usf.edu> worked out some thorny configuration details for securing the Apache/DODS/OPeNDAP combination.
  9. `$prefix' is `/usr/local/' unless you built the server from source code and specified a different root directory for its installation.
  10. We have reports that our Java DAP libraries work with versions as old as 1.2. jhrg 10/13/05.