svn commit: r1450036 - in /trafficserver/site/trunk/content/docs/trunk/admin: getting-started/index.en.mdtext reverse-proxy-http-redirects/index.en.mdtext

[ig...@apache.org]

Author: igalic
Date: Tue Feb 26 05:54:53 2013
New Revision: 1450036

URL: http://svn.apache.org/r1450036
Log:
Fix up getting started document to be slightly more useful

Also add some clarifications to the reverse proxy documentation.

Modified:
    trafficserver/site/trunk/content/docs/trunk/admin/getting-started/index.en.mdtext
    trafficserver/site/trunk/content/docs/trunk/admin/reverse-proxy-http-redirects/index.en.mdtext

Modified: trafficserver/site/trunk/content/docs/trunk/admin/getting-started/index.en.mdtext
URL: http://svn.apache.org/viewvc/trafficserver/site/trunk/content/docs/trunk/admin/getting-started/index.en.mdtext?rev=1450036&r1=1450035&r2=1450036&view=diff
==============================================================================
--- trafficserver/site/trunk/content/docs/trunk/admin/getting-started/index.en.mdtext (original)
+++ trafficserver/site/trunk/content/docs/trunk/admin/getting-started/index.en.mdtext Tue Feb 26 05:54:53 2013
@@ -27,9 +27,16 @@ you want to use. Traffic Server uses the
 
 A version is made of a version-triplet: *`MAJOR.MINOR.PATCH`*
 
-The most important thing that you need to know is that an even *`MINOR`* says
-that this is production stable release (such as 3.0.3 and 3.2.5) and an odd
-*`MINOR`* number means that the release is a release targeted at developers.
+The most important thing that you need to know is that an *even `MINOR`* marks
+a production stable release (such as 3.0.3 and 3.2.5), while an *odd
+`MINOR`* number marks a targeted at developers.
+
+Sometimes we speak of trunk, master, or when talking about actual releases, we
+will say "-unstable", or "-dev". All of these are interchangable: trunk or master
+or sometimes TIP or HEAD, refer to the latest code in a Version Control System.
+While "-dev" (or the unfortunately named "-unstable") signifies qualifies that
+a certain release "3.3.1-dev" is has not had seen enough testing to be seen as
+production ready.
 
 If your distribution does not come with a prepackaged Traffic Server, please
 go to [downloads](/downloads) to choose the version that you consider
@@ -37,7 +44,7 @@ most appropriate for yourself. If you wa
 you can clone our [git repository](https://git-wip-us.apache.org/repos/asf/trafficserver.git).
 
 Please note that while we do have a [GitHub Mirror](https://github.com/apache/trafficserver)
-that you can also use to submit pull requests, it is only updated once a day.
+that you can also use to submit pull requests, it may not be entirely up-to-date.
 
 # Building Traffic Server {#Building}
 
@@ -133,6 +140,9 @@ To run the `trafficserver start` command
 
         bin/trafficserver start
 
+At this point your server is up and running in the default configuration of a
+[reverse proxy](../reverse-proxy-http-redirects).
+
 # Start Traffic Line # {#StartTrafficLine}
 
 Traffic Line provides a quick way of viewing Traffic Server statistics and
@@ -147,19 +157,9 @@ For a list of `traffic_line` commands, e
 
      bin/traffic_line -h
 
-# Start Traffic Shell  # {#StartTrafficShell}
-
-Traffic Shell is a command-line tool that enables you to monitor and configure
-Traffic Server; it can be used instead of Traffic Line. Traffic Server provides
-documentation for Traffic Shell in the form of manual (`man`) pages.
-
-    bin/start_traffic_shell
-
-The `man` page describes how to use Traffic Shell, how to obtain a list of available
-commands, and how to obtain documentation about each command.
-
-    man traffic_shell
-
+Please note that `traffic_line`, while a fine tool for an administrator, is
+a poor choice for automation, especially that of monitoring. See our chapter on
+[Monitoring Traffic](../monitoring-traffic) for how to get that righter.
 
 # Stop Traffic Server  # {#StopTS}
 

Modified: trafficserver/site/trunk/content/docs/trunk/admin/reverse-proxy-http-redirects/index.en.mdtext
URL: http://svn.apache.org/viewvc/trafficserver/site/trunk/content/docs/trunk/admin/reverse-proxy-http-redirects/index.en.mdtext?rev=1450036&r1=1450035&r2=1450036&view=diff
==============================================================================
--- trafficserver/site/trunk/content/docs/trunk/admin/reverse-proxy-http-redirects/index.en.mdtext (original)
+++ trafficserver/site/trunk/content/docs/trunk/admin/reverse-proxy-http-redirects/index.en.mdtext Tue Feb 26 05:54:53 2013
@@ -127,6 +127,11 @@ The figure above demonstrates the follow
 To configure HTTP reverse proxy, you must perform the following tasks: 
 
 * Create mapping rules in the `remap.config` file (refer to [Creating Mapping Rules for HTTP Requests](#CreatingMappingRulesHTTPRequests)). 
+
+    :::text
+    # remap.config
+    map http://www.host.com http://realhost.com
+
 * Enable the reverse proxy option (refer to [Enabling HTTP Reverse Proxy](#EnablingHTTPReverseProxy)). 
 
 In addition to the tasks above, you can also [Set Optional HTTP Reverse Proxy 
@@ -179,16 +184,18 @@ a request URL, then Traffic Server appli
 ### reverse-map rule ### {#reversemaprule}
 
 A **reverse-map rule** translates the URL in origin server redirect responses to point to
-Traffic Server so that clients are redirected to Traffic Server instead of accessing an
+Traffic Server so that clients are **redirected** to Traffic Server instead of accessing an
 origin server directly. For example, if there is a directory `/pub` on an origin server at
 `www.molasses.com` and a client sends a request to that origin server for `/pub`, then the
-origin server might reply with a redirect to `http://www.test.com/pub/` to let the client know
-that it was a directory it had requested, not a document (a common use of redirects is to
-normalize URLs so that clients can bookmark documents properly). 
-
-Traffic Server uses reverse-map rules to prevent clients (that receive redirects from origin
-servers) from bypassing Traffic Server and directly accessing the origin servers. 
-
+origin server might reply with a redirect by sending the Header `Location: http://www.test.com/pub/`
+to let the client know that it was a directory it had requested, not a document (a common use of
+redirects is to normalize URLs so that clients can bookmark documents properly). 
+
+Traffic Server uses `reverse_map` rules to prevent clients (that receive redirects from origin
+servers) from bypassing Traffic Server and directly accessing the origin servers. In many cases
+the client would be hitting a wall because `realhost.com` actually does not resolve for the client.
+(E.g.: Because it's running on a port shielded by a firewall, or because it's running on a
+non-routable LAN IP)
 
 Both map and reverse-map rules consist of a **target** (origin) URL and a **replacement** 
 (destination) URL. In a **map rule**, the target URL points to Traffic Server