Return-Path: X-Original-To: apmail-trafficserver-commits-archive@www.apache.org Delivered-To: apmail-trafficserver-commits-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id B7AC3730C for ; Fri, 11 Nov 2011 21:26:47 +0000 (UTC) Received: (qmail 45432 invoked by uid 500); 11 Nov 2011 21:26:47 -0000 Delivered-To: apmail-trafficserver-commits-archive@trafficserver.apache.org Received: (qmail 45382 invoked by uid 500); 11 Nov 2011 21:26:47 -0000 Mailing-List: contact commits-help@trafficserver.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@trafficserver.apache.org Delivered-To: mailing list commits@trafficserver.apache.org Received: (qmail 45375 invoked by uid 99); 11 Nov 2011 21:26:47 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 11 Nov 2011 21:26:47 +0000 X-ASF-Spam-Status: No, hits=-2000.0 required=5.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [140.211.11.4] (HELO eris.apache.org) (140.211.11.4) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 11 Nov 2011 21:26:20 +0000 Received: from eris.apache.org (localhost [127.0.0.1]) by eris.apache.org (Postfix) with ESMTP id 696E22388AC8 for ; Fri, 11 Nov 2011 21:25:33 +0000 (UTC) Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Subject: svn commit: r798527 [7/19] - in /websites/staging/trafficserver/trunk/content/docs/trunk/sdk: ./ actions-guide/ adding-statistics/ continuations/ getting-started/ header-based-plugin-examples/ header-based-plugin-examples/basic-authorization-plugin/ he... Date: Fri, 11 Nov 2011 21:25:29 -0000 To: commits@trafficserver.apache.org From: buildbot@apache.org X-Mailer: svnmailer-1.0.8-patched Message-Id: <20111111212533.696E22388AC8@eris.apache.org> X-Virus-Checked: Checked by ClamAV on apache.org Modified: websites/staging/trafficserver/trunk/content/docs/trunk/sdk/http-headers/guide-to-trafficserver-http-header-system/duplicate-mime-fields-are-not-coalesced.en.html ============================================================================== --- websites/staging/trafficserver/trunk/content/docs/trunk/sdk/http-headers/guide-to-trafficserver-http-header-system/duplicate-mime-fields-are-not-coalesced.en.html (original) +++ websites/staging/trafficserver/trunk/content/docs/trunk/sdk/http-headers/guide-to-trafficserver-http-header-system/duplicate-mime-fields-are-not-coalesced.en.html Fri Nov 11 21:25:27 2011 @@ -4,7 +4,7 @@ xml:lang="en" lang="en"> - Apache Traffic Server™ Software Developers Kit + Duplicate MIME Fields Are Not Coalesced ### {#DuplicateMIMEFieldsAreNotCoalesced} @@ -24,7 +24,7 @@
-

Apache Traffic Server™ Software Developers Kit

+

Duplicate MIME Fields Are Not Coalesced ### {#DuplicateMIMEFieldsAreNotCoalesced}

@@ -54,8 +54,7 @@
-

Duplicate MIME Fields Are Not Coalesced

-

MIME headers can contain more than one MIME field with the same name. Earlier +

MIME headers can contain more than one MIME field with the same name. Earlier versions of Traffic Server joined multiple fields with the same name into one field with composite values. This behavior came at a performance cost and caused interoperability problems with older clients and servers. Therefore, this version @@ -66,7 +65,7 @@ and then iterate over the duplicate fiel

- +
Modified: websites/staging/trafficserver/trunk/content/docs/trunk/sdk/http-headers/guide-to-trafficserver-http-header-system/index.en.html ============================================================================== --- websites/staging/trafficserver/trunk/content/docs/trunk/sdk/http-headers/guide-to-trafficserver-http-header-system/index.en.html (original) +++ websites/staging/trafficserver/trunk/content/docs/trunk/sdk/http-headers/guide-to-trafficserver-http-header-system/index.en.html Fri Nov 11 21:25:27 2011 @@ -4,7 +4,7 @@ xml:lang="en" lang="en"> - Apache Traffic Server™ Software Developers Kit + Guide to Traffic Server HTTP Header System @@ -24,7 +24,7 @@
-

Apache Traffic Server™ Software Developers Kit

+

Guide to Traffic Server HTTP Header System

@@ -54,8 +54,7 @@
-

Guide to Traffic Server HTTP Header System

-

No Null-Terminated Strings

+

No Null-Terminated Strings

It's not safe to assume that string data contained in marshal buffers (such as URLs and MIME fields) is stored in null-terminated string copies. Therefore, your plugins should always use the length parameter when retrieving or manipulating @@ -84,7 +83,7 @@ or object requested does not exist.

- +
Modified: websites/staging/trafficserver/trunk/content/docs/trunk/sdk/http-headers/guide-to-trafficserver-http-header-system/mime-fields-always-belong-to-an-associated-mime-header.en.html ============================================================================== --- websites/staging/trafficserver/trunk/content/docs/trunk/sdk/http-headers/guide-to-trafficserver-http-header-system/mime-fields-always-belong-to-an-associated-mime-header.en.html (original) +++ websites/staging/trafficserver/trunk/content/docs/trunk/sdk/http-headers/guide-to-trafficserver-http-header-system/mime-fields-always-belong-to-an-associated-mime-header.en.html Fri Nov 11 21:25:27 2011 @@ -4,7 +4,7 @@ xml:lang="en" lang="en"> - Apache Traffic Server™ Software Developers Kit + MIME Fields Always Belong to an Associated MIME Header @@ -24,7 +24,7 @@
-

Apache Traffic Server™ Software Developers Kit

+

MIME Fields Always Belong to an Associated MIME Header

@@ -54,8 +54,7 @@
-

MIME Fields Always Belong to an Associated MIME Header

-

When using Traffic Server, you cannot create a new MIME field without an associated +

When using Traffic Server, you cannot create a new MIME field without an associated MIME header or HTTP header; MIME fields are always seen as part of a MIME header or HTTP header.

To use a MIME field, you must specify the MIME header or HTTP header to which @@ -98,7 +97,7 @@ the discussion of parent TSMLoc

- +
Modified: websites/staging/trafficserver/trunk/content/docs/trunk/sdk/http-headers/guide-to-trafficserver-http-header-system/release-marshal-buffer-handles.en.html ============================================================================== --- websites/staging/trafficserver/trunk/content/docs/trunk/sdk/http-headers/guide-to-trafficserver-http-header-system/release-marshal-buffer-handles.en.html (original) +++ websites/staging/trafficserver/trunk/content/docs/trunk/sdk/http-headers/guide-to-trafficserver-http-header-system/release-marshal-buffer-handles.en.html Fri Nov 11 21:25:27 2011 @@ -4,7 +4,7 @@ xml:lang="en" lang="en"> - Apache Traffic Server™ Software Developers Kit + Release Marshal Buffer Handles @@ -24,7 +24,7 @@
-

Apache Traffic Server™ Software Developers Kit

+

Release Marshal Buffer Handles

@@ -54,8 +54,7 @@
-

Release Marshal Buffer Handles

-

When you fetch a component object or create a new object, you get back a +

When you fetch a component object or create a new object, you get back a handle to the object location. The handle is either an TSMLoc for an object location or char * for a string location. You can manipulate the object through these handles, but when you are finished you need to release the @@ -108,7 +107,7 @@ words, call TSHandleMLocRelease

- +