trafficserver-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From iga...@apache.org
Subject svn commit: r1030650 - in /trafficserver/site/branches/ats-cms/content: ./ docs/admin/ docs/sdk/ docs/trunk/ docs/trunk/admin/ docs/trunk/sdk/
Date Wed, 03 Nov 2010 20:32:17 GMT
Author: igalic
Date: Wed Nov  3 20:32:16 2010
New Revision: 1030650

URL: http://svn.apache.org/viewvc?rev=1030650&view=rev
Log:
Moving docs/* to docs/trunk, for versioning.
renaming foo.mdtext to foo.en.mdtext in preparation for translations,
renaming links from foo.html? to foo, refer to:
http://httpd.apache.org/docs/current/content-negotiation.html#naming

Added:
    trafficserver/site/branches/ats-cms/content/docs/trunk/
    trafficserver/site/branches/ats-cms/content/docs/trunk/admin/
      - copied from r1030647, trafficserver/site/branches/ats-cms/content/docs/admin/
    trafficserver/site/branches/ats-cms/content/docs/trunk/admin/files.en.mdtext
      - copied, changed from r1030647, trafficserver/site/branches/ats-cms/content/docs/admin/files.mdtext
    trafficserver/site/branches/ats-cms/content/docs/trunk/admin/index.en.mdtext
      - copied, changed from r1030647, trafficserver/site/branches/ats-cms/content/docs/admin/index.mdtext
    trafficserver/site/branches/ats-cms/content/docs/trunk/sdk/
      - copied from r1030647, trafficserver/site/branches/ats-cms/content/docs/sdk/
Removed:
    trafficserver/site/branches/ats-cms/content/docs/admin/
    trafficserver/site/branches/ats-cms/content/docs/sdk/
    trafficserver/site/branches/ats-cms/content/docs/trunk/admin/files.mdtext
    trafficserver/site/branches/ats-cms/content/docs/trunk/admin/index.mdtext
    trafficserver/site/branches/ats-cms/content/downloads.mdtext
    trafficserver/site/branches/ats-cms/content/index.mdtext

Copied: trafficserver/site/branches/ats-cms/content/docs/trunk/admin/files.en.mdtext (from
r1030647, trafficserver/site/branches/ats-cms/content/docs/admin/files.mdtext)
URL: http://svn.apache.org/viewvc/trafficserver/site/branches/ats-cms/content/docs/trunk/admin/files.en.mdtext?p2=trafficserver/site/branches/ats-cms/content/docs/trunk/admin/files.en.mdtext&p1=trafficserver/site/branches/ats-cms/content/docs/admin/files.mdtext&r1=1030647&r2=1030650&rev=1030650&view=diff
==============================================================================
--- trafficserver/site/branches/ats-cms/content/docs/admin/files.mdtext (original)
+++ trafficserver/site/branches/ats-cms/content/docs/trunk/admin/files.en.mdtext Wed Nov 
3 20:32:16 2010
@@ -253,7 +253,7 @@ Server bin directory; then run the `traf
 changes. When you apply the changes to a node in a cluster, Traffic Server
 automatically applies the changes to all other nodes in the cluster.
 Traffic Server uses the `congestion.config` file only if you enable the
-[Congestion Control](http.html#UsingCongestionControl) option.
+[Congestion Control](http#UsingCongestionControl) option.
 
 You can create rules in the congestion.config file to specify:
 - Which origin servers Traffic Server tracks for congestion.
@@ -411,12 +411,12 @@ The `hosting.config` file enables you to
 origin servers and/or domains so that you can manage cache space
 efficiently and restrict disk usage. For step-by-step instructions on
 partitioning the cache according to origin servers and/or domains, refer
-to [Partitioning the Cache](cache.html) According to Origin Server or Domain.
+to [Partitioning the Cache](cache) According to Origin Server or Domain.
 Before you can assign cache partitions to specific origin servers and/or
 domains, you must first partition your cache according to size and
 protocol in the [partition.config](#partition.config) file.
 For step-by-step instructions about partitioning your cache, refer to
-[Partitioning the Cache](cache.html). For a description of the
+[Partitioning the Cache](cache). For a description of the
 `partition.config` file, refer to [partition.config](#partition.config).
 
 After you modify hosting.config, navigate to the Traffic Server bin
@@ -584,12 +584,12 @@ The `logs.config` file establishes and f
 custom transaction log files.
 Although Traffic Server supports traditional custom logging, you
 should use the more versatile XML-based custom logging (refer to
-[Using the Custom Format](log.html) and
+[Using the Custom Format](log) and
 [logs\_xml.config](#logs_xml.config)). If you opt to use
 traditional custom logging instead of the more versatile XML-based
 custom logging, then you must enable the traditional custom logging
 option manually (refer to
-[Support for Traditional Custom Logging](log.htm)).
+[Support for Traditional Custom Logging](log)).
 
 **IMPORTANT:** After you modify `logs.config`, navigate to the
 Traffic Server`bin` directory and run the `traffic_line -x` command
@@ -623,7 +623,7 @@ separated by colons (:).
 *`format string`*
 :  Identifies the `printf` -style format string specifying the field
    symbols to be displayed and how they should look in ASCII. Refer to
-   this [Appendix](logfmts.htm) for a list of the available field
+   this [Appendix](logfmts) for a list of the available field
    symbols and their meanings.
 
    Field symbols are indicated by %<`field_symbol` \> format. For
@@ -683,7 +683,7 @@ out the following section at the end of 
 To record HTTP transactions for different origin servers in
 separate log files, you must list each origin server hostname in
 the `log_hosts.config` file. In addition, you must enable the
-[HTTP Host Log Splitting](log.html) option. You should use the same
+[HTTP Host Log Splitting](log) option. You should use the same
 `log_hosts.config` file on every Traffic Server node in your
 cluster. After you modify the `log_hosts.config` file,
 navigate to the Traffic Server`bin` directory and run the
@@ -763,7 +763,7 @@ The following list shows **`LogFormat`**
    describing each log entry when formatted for ASCII output. Use
    `%<` `*field*` `>` as a placeholder for valid field names. For
    more information, refer to
-   [Custom Logging Fields](logfmts.html#custom-logging-fields).
+   [Custom Logging Fields](logfmts#custom-logging-fields).
 
    The specified field can be one of the following types:
 
@@ -804,7 +804,7 @@ The following list shows the `LogFilter`
 
    **`valid\_log\_field`** - the field that will be compared against
    the given value. For more information, refer to
-   [Logging Format Cross-Reference](logfmts.html#cross-reference).
+   [Logging Format Cross-Reference](logfmts#cross-reference).
 
    **`valid\_operator\_field`** - any one of the following: `MATCH`,
    `CASE_INSENSITIVE_MATCH`, `CONTAIN`, `CASE_INSENSITIVE_CONTAIN`.
@@ -852,7 +852,7 @@ The following list shows the `LogObject`
    If the name does not contain an extension (for example, `squid`),
    then the extension `.log` is automatically appended to it for ASCII
    logs and `.blog` for binary logs (refer to
-   [Mode = "valid\_logging\_mode"](files.htm#0_73225)).
+   [Mode = "valid\_logging\_mode"](files#0_73225)).
 
    If you do not want an extension to be added, then end the filename with a
    single (.) dot (for example: `squid.` ).
@@ -1042,7 +1042,7 @@ configuration:
 
 Traffic Server uses the `parent.config` file only when the parent
 caching option is enabled (refer to
-[Configuring Traffic Server to Use a Parent Cache](hier.html)).
+[Configuring Traffic Server to Use a Parent Cache](hier)).
 
 **IMPORTANT:** After you modify the `parent.config` file, navigate
 to the Traffic Server`bin` directory and run the `traffic_line -x`
@@ -1166,7 +1166,7 @@ the [hosting.config](#hosting.config) fi
 nodes in a cluster. You must stop Traffic Server before you change
 the cache partition size and protocol assignment. For step-by-step
 instructions about partitioning the cache, refer to
-[Partitioning the Cache](cache.html).
+[Partitioning the Cache](cache).
 
 
 #### Format ####
@@ -1334,7 +1334,7 @@ the `records.config` file.
 :  `LOG_DAEMON`
 :  The facility used to record system log files.
    Refer to
-   [Understanding Traffic Server Log Files](log.htm#UnderstandingTrafficEdgeLogFiles).
+   [Understanding Traffic Server Log Files](log#UnderstandingTrafficEdgeLogFiles).
 
 *`proxy.config.cop.core_signal`*
 :  `INT`
@@ -1546,7 +1546,7 @@ the `records.config` file.
    `2` = some extra information is added.
 
    Note: the Via: header string interpretation is
-   [documented here.](trouble.htm#interpret_via_header)
+   [documented here.](trouble#interpret_via_header)
 
 
 *`proxy.config.http.insert_response_via_str `*
@@ -1606,7 +1606,7 @@ the `records.config` file.
 :  `0`
 :  Enables (`1`) or disables (`0`) the parent caching option.
 
-   Refer to [Hierarchical Caching](hier.html).
+   Refer to [Hierarchical Caching](hier).
 
 *`proxy.config.http.parent_proxy.retry_time `*
 :  `INT`
@@ -1803,7 +1803,7 @@ the `records.config` file.
    client a message to retry the congested origin server later.
 
    Refer to
-   [Using Congestion Control](http.htm#UsingCongestionControl).
+   [Using Congestion Control](http#UsingCongestionControl).
 
 
 **Negative Response Caching**
@@ -2229,7 +2229,7 @@ the `records.config` file.
    for the selection specification.
 
    Refer to
-   [Configuring DNS Server Selection (Split DNS)](secure.html#ConfiguringDNSServerSelectionSplit).
+   [Configuring DNS Server Selection (Split DNS)](secure#ConfiguringDNSServerSelectionSplit).
 
 *`proxy.config.dns.splitdns.def_domain`*
 :  `STRING`
@@ -2330,7 +2330,7 @@ the `records.config` file.
    `2` = log transactions only  
    `3` = full logging (errors + transactions)
 
-   Refer to [Working with Log Files](log.htm).
+   Refer to [Working with Log Files](log).
 
 *`proxy.config.log2.max_secs_per_buffer`*
 :  `INT`
@@ -2511,7 +2511,7 @@ the `records.config` file.
    log file for HTTP transactions for each origin server listed in the
    `log_hosts.config` file.
 
-   Refer to [HTTP Host Log Splitting](log.html#HTTPHostLogSplitting).
+   Refer to [HTTP Host Log Splitting](log#HTTPHostLogSplitting).
 
 *`proxy.local.log2.collation_mode`*
 :  `INT`
@@ -2530,7 +2530,7 @@ the `records.config` file.
 
    For information on sending XML-based custom formats to the
    collation server, refer to
-   [logs\_xml.config](files.htm#logs_xml.config).
+   [logs\_xml.config](files#logs_xml.config).
 
    **Note:** Although Traffic Server supports traditional custom
    logging, you should use the more versatile XML-based custom
@@ -2717,7 +2717,7 @@ the `records.config` file.
 :  `INT`
 :  `0`
 :  Enables (`1`) or disables (`0`) the
-   [SSL Termination](secure.htm#UsingSSLTermination) option.
+   [SSL Termination](secure#UsingSSLTermination) option.
 
 *`proxy.config.ssl.SSLv2`*
 :  `INT`
@@ -2878,7 +2878,7 @@ the `records.config` file.
    `1` = allows Traffic Server to receive ICP queries only  
    `2` = allows Traffic Server to send and receive ICP queries
 
-   Refer to [ICP Peering](hier.html#ICPPeering).
+   Refer to [ICP Peering](hier#ICPPeering).
 
 *`proxy.config.icp.icp_interface`*
 :  `STRING`
@@ -3033,7 +3033,7 @@ uses to perform the following actions:
 -   Redirect HTTP requests permanently or temporarily without
     Traffic Server having to contact any origin servers
 
-Refer to [Reverse Proxy and HTTP Redirects](reverse.htm), for
+Refer to [Reverse Proxy and HTTP Redirects](reverse), for
 information about redirecting HTTP requests and using reverse
 proxy.
 
@@ -3222,7 +3222,7 @@ This will pass "1" and "2" to plugin1.so
 The `splitdns.config` file enables you to specify the DNS server
 that Traffic Server should use for resolving hosts under specific
 conditions. For more information, refer to
-[Configuring DNS Server Selection (Split DNS)](secure.htm).
+[Configuring DNS Server Selection (Split DNS)](secure).
 
 To specify a DNS server, you must supply the following information
 in each active line within the file:

Copied: trafficserver/site/branches/ats-cms/content/docs/trunk/admin/index.en.mdtext (from
r1030647, trafficserver/site/branches/ats-cms/content/docs/admin/index.mdtext)
URL: http://svn.apache.org/viewvc/trafficserver/site/branches/ats-cms/content/docs/trunk/admin/index.en.mdtext?p2=trafficserver/site/branches/ats-cms/content/docs/trunk/admin/index.en.mdtext&p1=trafficserver/site/branches/ats-cms/content/docs/admin/index.mdtext&r1=1030647&r2=1030650&rev=1030650&view=diff
==============================================================================
--- trafficserver/site/branches/ats-cms/content/docs/admin/index.mdtext (original)
+++ trafficserver/site/branches/ats-cms/content/docs/trunk/admin/index.en.mdtext Wed Nov 
3 20:32:16 2010
@@ -65,7 +65,7 @@ satisfy future requests.
 Traffic Server provides explicit proxy caching, in which the user’s
 client software must be configured to send requests directly to Traffic
 Server. Explicit proxy caching is described in the
-[Explicit Proxy Caching](/docs/admin/explicit.html) section.
+[Explicit Proxy Caching](/docs/admin/explicit) section.
 
 ### Traffic Server as a Reverse Proxy ### {#reverse-proxy}
 As a reverse proxy, Traffic Server is configured to be the origin
@@ -73,7 +73,7 @@ server to which the user is trying to co
 server’s advertised hostname resolves to Traffic Server, which acts as
 the real origin server). The reverse proxy feature is also called
 server acceleration. Reverse proxy is described in more detail in
-[Reverse Proxy and HTTP Redirects](/docs/admin/reverse.html).
+[Reverse Proxy and HTTP Redirects](/docs/admin/reverse).
 
 ### Traffic Server in a Cache Hierarchy ### {#cache-hierachy}
 Traffic Server can participate in flexible cache hierarchies, in which
@@ -85,7 +85,7 @@ to similar caching products.
 
 Traffic Server supports ICP (Internet Cache Protocol) peering.
 Hierarchical caching is described in more detail in
-[Hierarchical Caching](/docs/admin/hier.html).
+[Hierarchical Caching](/docs/admin/hier).
 
 ## Traffic Server Components ## {#ats-components}
 Traffic Server consists of several components that work together to
@@ -109,7 +109,7 @@ If all of the cache disks fail, then Tra
 proxy-only mode. You can partition the cache to reserve a certain
 amount of disk space for storing data for specific protocols and origin
 servers. For more information about the cache, see
-[Configuring the Cache](/docs/admin/cache.html).
+[Configuring the Cache](/docs/admin/cache).
 
 ### The RAM Cache ### {#ram-cache}
 Traffic Server maintains a small RAM cache that contains extremely
@@ -117,7 +117,7 @@ popular objects. This RAM cache serves t
 as possible and reduces load on disks, especially during temporary
 traffic peaks. You can configure the RAM cache size to suit your needs;
 for detailed information, refer to
-[Changing the Size of the RAM Cache](/docs/admin/cache.html#ChangingSizeRAMCache).
+[Changing the Size of the RAM Cache](/docs/admin/cache#ChangingSizeRAMCache).
 
 ### The Host Database ### {#host-db}
 The Traffic Server host database stores the domain name server (DNS)
@@ -210,9 +210,9 @@ and monitoring:
   they contain information specific to protocol or hosts.
 
 Traffic analysis options are described in more detail in
-[Monitoring Traffic](/docs/admin/monitor.html);
+[Monitoring Traffic](/docs/admin/monitor);
 Traffic Server logging options are described in
-[Working with Log Files](/docs/admin/log.html).
+[Working with Log Files](/docs/admin/log).
 
 ## Traffic Server Security Options ## {#security}
 Traffic Server provides numerous options that enable you to establish
@@ -234,5 +234,5 @@ following:
 * Control access via SSL (Secure Sockets Layer).
 
 Traffic Server security options are described in more detail in
-[Security Options](/docs/admin/secure.html).
+[Security Options](/docs/admin/secure).
 



Mime
View raw message