Differences

This shows you the differences between two versions of the page.

--- en:user:gs2_urls [2017/02/20 00:14] – kjdon
+++ en:user:gs2_urls [2023/03/13 01:46] (current) – external edit 127.0.0.1
@@ Line 1: / Line 1: @@
 ====== Greenstone2 URLs======
@@ Line 102: / Line 105: @@
 ===== Redirecting a link to Greenstone =====
-<!-- id:276 -->You may want to redirect a more convenient URL to your Greenstone cgi program. For example, on our system the URL // http:%%//%%nzdl.org // (which is shorthand for // http:%%//%%nzdl.org/index.html) // is redirected to // http:%%//%%nzdl.org/cgi-bin/library //. The Apache webserver accomplishes this with the //Redirect// directive. Along with other directives, this goes into the //C:\Program Files\Apache Group\Apache\conf\httpd.conf// configuration file. To redirect the URL // http:%%//%%www.yourserver.com // to // http:%%//%%www.yourserver.com/cgi-bin/library //, put this line into //httpd.conf//:
+You may want to redirect a more convenient URL to your Greenstone cgi program. For example, on our system the URL // http:%%//%%nzdl.org // (which is shorthand for // http:%%//%%nzdl.org/index.html) // is redirected to // http:%%//%%nzdl.org/cgi-bin/library //. The Apache webserver accomplishes this with the //Redirect// directive. Along with other directives, this goes into the //C:\Program Files\Apache Group\Apache\conf\httpd.conf// configuration file. To redirect the URL // http:%%//%%www.yourserver.com // to // http:%%//%%www.yourserver.com/cgi-bin/library //, put this line into //httpd.conf//:
 <code>
@@ Line 108: / Line 111: @@
 </code>
-<!-- id:277 -->Then you will reach your digital library system directly from the URL // http:%%//%%www.yourserver.com //. Instead, if you wanted a URL like // http:%%//%%www.yourserver.com/greenstone // to be redirected to // http:%%//%%www.yourserver.com/cgi-bin/library //, include in the //httpd.conf// file
+Then you will reach your digital library system directly from the URL // http:%%//%%www.yourserver.com //. Instead, if you wanted a URL like // http:%%//%%www.yourserver.com/greenstone // to be redirected to // http:%%//%%www.yourserver.com/cgi-bin/library //, include in the //httpd.conf// file
 <code>
@@ Line 114: / Line 117: @@
 </code>
-<!-- id:278 -->If your computer doesn't have a domain name (like the “www.yourserver.com” above), just replace // www.yourserver.com // by // localhost // in the lines above. So long as the browser is running on the same machine as the webserver—which it surely is if your computer doesn't have a domain name—this has the same effect as the above redirections.
+If your computer doesn't have a domain name (like the “www.yourserver.com” above), just replace // www.yourserver.com // by // localhost // in the lines above. So long as the browser is running on the same machine as the webserver—which it surely is if your computer doesn't have a domain name—this has the same effect as the above redirections.
-<!-- id:279 -->Instead of putting redirect directives into the file //httpd.conf//, you can equally well put them into a file called //.htaccess// within your server's document root directory. In fact, doing so has two advantages. First, changes to //.htaccess// take effect immediately, whereas you have to restart the Apache webserver to see the effect of changes to //httpd.conf//. Second, on Unix systems you usually have to be logged in as the “root” user to edit //httpd.conf//, whereas you don't to edit //.htaccess//.
+Instead of putting redirect directives into the file //httpd.conf//, you can equally well put them into a file called //.htaccess// within your server's document root directory. In fact, doing so has two advantages. First, changes to //.htaccess// take effect immediately, whereas you have to restart the Apache webserver to see the effect of changes to //httpd.conf//. Second, on Unix systems you usually have to be logged in as the “root” user to edit //httpd.conf//, whereas you don't to edit //.htaccess//.