Wiki Testing/ServerInstallationGuideFootnotes: Difference between revisions

From OPeNDAP Documentation
⧼opendap2-jumptonavigation⧽
(New page: ===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...)
 
 
(15 intermediate revisions by the same user not shown)
Line 1: Line 1:
===1===
= Citations =
    http://spg.gsfc.nasa.gov/rfc/004  
 
===2===
<references/>
    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===
= References =
    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===
*<cite id=ref1>http://spg.gsfc.nasa.gov/rfc/004 </cite>
    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.  
*<cite id=ref2> 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. </cite>
===5===
*<cite id=ref3> 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.</cite>
    A user has contributed examples for this. Go to http://seawater.tamu.edu/noppdodsgom and click on "Resources."  
*<cite id=ref4> 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. </cite>
===6===
*<cite id=ref5> A user has contributed examples for this. Go to http://seawater.tamu.edu/noppdodsgom and click on "Resources." </cite>
    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.  
*<cite id=ref6>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. </cite>
===7===
*<cite id=ref7>...also tested on Apache 2.0.40, 07/25/03 jhrg </cite>
    ...also tested on Apache 2.0.40, 07/25/03 jhrg  
*<cite id=ref8>Brock Murch <bmurch@marine.usf.edu> worked out some thorny configuration details for securing the Apache/DODS/OPeNDAP combination. </cite>
===8===
*<cite id=ref9>`$prefix' is `/usr/local/' unless you built the server from source code and specified a different root directory for its installation. </cite>
    Brock Murch <bmurch@marine.usf.edu> worked out some thorny configuration details for securing the Apache/DODS/OPeNDAP combination.  
*<cite id=ref10> We have reports that our Java DAP libraries work with versions as old as 1.2. jhrg 10/13/05.</cite>
===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.

Latest revision as of 11:15, 3 January 2008

Citations

<references/>

References

  • http://spg.gsfc.nasa.gov/rfc/004
  • 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.
  • 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.
  • 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.
  • A user has contributed examples for this. Go to http://seawater.tamu.edu/noppdodsgom and click on "Resources."
  • 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.
  • ...also tested on Apache 2.0.40, 07/25/03 jhrg
  • Brock Murch <bmurch@marine.usf.edu> worked out some thorny configuration details for securing the Apache/DODS/OPeNDAP combination.
  • `$prefix' is `/usr/local/' unless you built the server from source code and specified a different root directory for its installation.
  • We have reports that our Java DAP libraries work with versions as old as 1.2. jhrg 10/13/05.
Retrieved from "https://docs.opendap.org/index.php?title=Wiki_Testing/ServerInstallationGuideFootnotes&oldid=1499"