You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@trafficserver.apache.org by bu...@apache.org on 2011/12/19 23:58:08 UTC
svn commit: r800542 [1/23] - in
/websites/staging/trafficserver/trunk/content/docs/v2: ./ admin/
admin/images/ sdk/ sdk/css/ sdk/images/ sdk/images/docbook/ sdk/js/
Author: buildbot
Date: Mon Dec 19 22:58:01 2011
New Revision: 800542
Log:
Staging update by buildbot
Added:
websites/staging/trafficserver/trunk/content/docs/v2/
websites/staging/trafficserver/trunk/content/docs/v2/.htaccess
websites/staging/trafficserver/trunk/content/docs/v2/admin/
websites/staging/trafficserver/trunk/content/docs/v2/admin/Glossary.htm (with props)
websites/staging/trafficserver/trunk/content/docs/v2/admin/TE_Admin_v1_5_deprecated.pdf (with props)
websites/staging/trafficserver/trunk/content/docs/v2/admin/bottom.html (with props)
websites/staging/trafficserver/trunk/content/docs/v2/admin/cache.htm (with props)
websites/staging/trafficserver/trunk/content/docs/v2/admin/cli.htm (with props)
websites/staging/trafficserver/trunk/content/docs/v2/admin/configure.htm (with props)
websites/staging/trafficserver/trunk/content/docs/v2/admin/doc.css (with props)
websites/staging/trafficserver/trunk/content/docs/v2/admin/errors.htm (with props)
websites/staging/trafficserver/trunk/content/docs/v2/admin/explicit.htm (with props)
websites/staging/trafficserver/trunk/content/docs/v2/admin/files.htm (with props)
websites/staging/trafficserver/trunk/content/docs/v2/admin/getstart.htm (with props)
websites/staging/trafficserver/trunk/content/docs/v2/admin/hier.htm (with props)
websites/staging/trafficserver/trunk/content/docs/v2/admin/http.htm (with props)
websites/staging/trafficserver/trunk/content/docs/v2/admin/images/
websites/staging/trafficserver/trunk/content/docs/v2/admin/images/alarm.jpg (with props)
websites/staging/trafficserver/trunk/content/docs/v2/admin/images/cache_hit.jpg (with props)
websites/staging/trafficserver/trunk/content/docs/v2/admin/images/cache_miss.jpg (with props)
websites/staging/trafficserver/trunk/content/docs/v2/admin/images/cachehrc.jpg (with props)
websites/staging/trafficserver/trunk/content/docs/v2/admin/images/configur.jpg (with props)
websites/staging/trafficserver/trunk/content/docs/v2/admin/images/dash.jpg (with props)
websites/staging/trafficserver/trunk/content/docs/v2/admin/images/dash3.jpg (with props)
websites/staging/trafficserver/trunk/content/docs/v2/admin/images/firewall.jpg (with props)
websites/staging/trafficserver/trunk/content/docs/v2/admin/images/httprvs.jpg (with props)
websites/staging/trafficserver/trunk/content/docs/v2/admin/images/logcolat.jpg (with props)
websites/staging/trafficserver/trunk/content/docs/v2/admin/images/monitor.jpg (with props)
websites/staging/trafficserver/trunk/content/docs/v2/admin/images/netscape_common_format.jpg (with props)
websites/staging/trafficserver/trunk/content/docs/v2/admin/images/netscape_extended2_format.jpg (with props)
websites/staging/trafficserver/trunk/content/docs/v2/admin/images/netscape_extended_format.jpg (with props)
websites/staging/trafficserver/trunk/content/docs/v2/admin/images/process.jpg (with props)
websites/staging/trafficserver/trunk/content/docs/v2/admin/images/records.jpg (with props)
websites/staging/trafficserver/trunk/content/docs/v2/admin/images/revproxy.jpg (with props)
websites/staging/trafficserver/trunk/content/docs/v2/admin/images/squid_format.jpg (with props)
websites/staging/trafficserver/trunk/content/docs/v2/admin/images/ssl_c.jpg (with props)
websites/staging/trafficserver/trunk/content/docs/v2/admin/images/ssl_os.jpg (with props)
websites/staging/trafficserver/trunk/content/docs/v2/admin/images/stat.jpg (with props)
websites/staging/trafficserver/trunk/content/docs/v2/admin/images/summary-mixt.log_file.jpg (with props)
websites/staging/trafficserver/trunk/content/docs/v2/admin/index.html (with props)
websites/staging/trafficserver/trunk/content/docs/v2/admin/intro.htm (with props)
websites/staging/trafficserver/trunk/content/docs/v2/admin/leftnav.html (with props)
websites/staging/trafficserver/trunk/content/docs/v2/admin/log.htm (with props)
websites/staging/trafficserver/trunk/content/docs/v2/admin/logfmts.htm (with props)
websites/staging/trafficserver/trunk/content/docs/v2/admin/monitor.htm (with props)
websites/staging/trafficserver/trunk/content/docs/v2/admin/preface.htm (with props)
websites/staging/trafficserver/trunk/content/docs/v2/admin/reverse.htm (with props)
websites/staging/trafficserver/trunk/content/docs/v2/admin/secure.htm (with props)
websites/staging/trafficserver/trunk/content/docs/v2/admin/template.html
websites/staging/trafficserver/trunk/content/docs/v2/admin/top.html (with props)
websites/staging/trafficserver/trunk/content/docs/v2/admin/trouble.htm (with props)
websites/staging/trafficserver/trunk/content/docs/v2/admin/ts_admin_chinese.pdf (with props)
websites/staging/trafficserver/trunk/content/docs/v2/sdk/
websites/staging/trafficserver/trunk/content/docs/v2/sdk/ASimplePlugin.html (with props)
websites/staging/trafficserver/trunk/content/docs/v2/sdk/AccessPluginFiles.html (with props)
websites/staging/trafficserver/trunk/content/docs/v2/sdk/AccessingTransactionProc.html (with props)
websites/staging/trafficserver/trunk/content/docs/v2/sdk/ActionFunctions.html (with props)
websites/staging/trafficserver/trunk/content/docs/v2/sdk/ActionsGuide.html (with props)
websites/staging/trafficserver/trunk/content/docs/v2/sdk/ActivateContinuations.html (with props)
websites/staging/trafficserver/trunk/content/docs/v2/sdk/AddingHooks.html (with props)
websites/staging/trafficserver/trunk/content/docs/v2/sdk/AddingStatistics.html (with props)
websites/staging/trafficserver/trunk/content/docs/v2/sdk/AlternateSelectionFunctions.html (with props)
websites/staging/trafficserver/trunk/content/docs/v2/sdk/App_DeprecatedFunctions.html (with props)
websites/staging/trafficserver/trunk/content/docs/v2/sdk/App_SampleSourceCode.html (with props)
websites/staging/trafficserver/trunk/content/docs/v2/sdk/App_Troubleshooting.html (with props)
websites/staging/trafficserver/trunk/content/docs/v2/sdk/AppendTransformPlugin.html (with props)
websites/staging/trafficserver/trunk/content/docs/v2/sdk/BasicAuthorizatonPlugin.html (with props)
websites/staging/trafficserver/trunk/content/docs/v2/sdk/BlacklistPlugin.html (with props)
websites/staging/trafficserver/trunk/content/docs/v2/sdk/CacheAPI.html (with props)
websites/staging/trafficserver/trunk/content/docs/v2/sdk/CacheAPI_Example.html (with props)
websites/staging/trafficserver/trunk/content/docs/v2/sdk/CacheInterfaceFunctions.html (with props)
websites/staging/trafficserver/trunk/content/docs/v2/sdk/ConceptIndex.html (with props)
websites/staging/trafficserver/trunk/content/docs/v2/sdk/ContinuationFunctions.html (with props)
websites/staging/trafficserver/trunk/content/docs/v2/sdk/Continuations.html (with props)
websites/staging/trafficserver/trunk/content/docs/v2/sdk/Conventions.html (with props)
websites/staging/trafficserver/trunk/content/docs/v2/sdk/CoupledStatistics.html (with props)
websites/staging/trafficserver/trunk/content/docs/v2/sdk/CoupledStatsFunctions.html (with props)
websites/staging/trafficserver/trunk/content/docs/v2/sdk/CreatingTSPlugins.html (with props)
websites/staging/trafficserver/trunk/content/docs/v2/sdk/CustInstallLicenseFunctions.html (with props)
websites/staging/trafficserver/trunk/content/docs/v2/sdk/DebuggingFunctions.html (with props)
websites/staging/trafficserver/trunk/content/docs/v2/sdk/Dep_IOBufferInterface.html (with props)
websites/staging/trafficserver/trunk/content/docs/v2/sdk/Dep_MutexFunctions.html (with props)
websites/staging/trafficserver/trunk/content/docs/v2/sdk/DeprecatedMarshBufFuncs.html (with props)
websites/staging/trafficserver/trunk/content/docs/v2/sdk/DoACacheRemove.html (with props)
websites/staging/trafficserver/trunk/content/docs/v2/sdk/DoACacheWrite.html (with props)
websites/staging/trafficserver/trunk/content/docs/v2/sdk/DuplicateMIMEFlds.html (with props)
websites/staging/trafficserver/trunk/content/docs/v2/sdk/Errors_Cache.html (with props)
websites/staging/trafficserver/trunk/content/docs/v2/sdk/FunctionIndex.html (with props)
websites/staging/trafficserver/trunk/content/docs/v2/sdk/FunctionReference.html (with props)
websites/staging/trafficserver/trunk/content/docs/v2/sdk/GenerateLicenseKey.html (with props)
websites/staging/trafficserver/trunk/content/docs/v2/sdk/GetingStarted.html (with props)
websites/staging/trafficserver/trunk/content/docs/v2/sdk/GuideTSHTTPHdrSyst.html (with props)
websites/staging/trafficserver/trunk/content/docs/v2/sdk/HTTPAlternateSelection.html (with props)
websites/staging/trafficserver/trunk/content/docs/v2/sdk/HTTPFunctions.html (with props)
websites/staging/trafficserver/trunk/content/docs/v2/sdk/HTTPHeaderFunctions.html (with props)
websites/staging/trafficserver/trunk/content/docs/v2/sdk/HTTPHeaders.html (with props)
websites/staging/trafficserver/trunk/content/docs/v2/sdk/HTTPHeaders2.html (with props)
websites/staging/trafficserver/trunk/content/docs/v2/sdk/HTTPHooksAndTransactions.html (with props)
websites/staging/trafficserver/trunk/content/docs/v2/sdk/HTTPSessionFunctions.html (with props)
websites/staging/trafficserver/trunk/content/docs/v2/sdk/HTTPSessions.html (with props)
websites/staging/trafficserver/trunk/content/docs/v2/sdk/HTTPTransactionFunctions.html (with props)
websites/staging/trafficserver/trunk/content/docs/v2/sdk/HTTPTransformationPlugins.html (with props)
websites/staging/trafficserver/trunk/content/docs/v2/sdk/HTTP_Transactions.html (with props)
websites/staging/trafficserver/trunk/content/docs/v2/sdk/HeaderBasedPluginEx.html (with props)
websites/staging/trafficserver/trunk/content/docs/v2/sdk/HostLookupFunctions.html (with props)
websites/staging/trafficserver/trunk/content/docs/v2/sdk/HostsLookupAPI.html (with props)
websites/staging/trafficserver/trunk/content/docs/v2/sdk/INKActionDone.html (with props)
websites/staging/trafficserver/trunk/content/docs/v2/sdk/INKAssert.html (with props)
websites/staging/trafficserver/trunk/content/docs/v2/sdk/INKCacheKeyDestroy.html (with props)
websites/staging/trafficserver/trunk/content/docs/v2/sdk/INKCacheKeyDigestSet.html (with props)
websites/staging/trafficserver/trunk/content/docs/v2/sdk/INKCacheKeyHostNameSet.html (with props)
websites/staging/trafficserver/trunk/content/docs/v2/sdk/INKCacheKeyPinnedSet.html (with props)
websites/staging/trafficserver/trunk/content/docs/v2/sdk/INKCacheRead.html (with props)
websites/staging/trafficserver/trunk/content/docs/v2/sdk/INKCacheReady.html (with props)
websites/staging/trafficserver/trunk/content/docs/v2/sdk/INKCacheRemove.html (with props)
websites/staging/trafficserver/trunk/content/docs/v2/sdk/INKCacheWrite.html (with props)
websites/staging/trafficserver/trunk/content/docs/v2/sdk/INKConfigGet.html (with props)
websites/staging/trafficserver/trunk/content/docs/v2/sdk/INKConfigRelease.html (with props)
websites/staging/trafficserver/trunk/content/docs/v2/sdk/INKConfigSet.html (with props)
websites/staging/trafficserver/trunk/content/docs/v2/sdk/INKContCreate.html (with props)
websites/staging/trafficserver/trunk/content/docs/v2/sdk/INKContDataGet.html (with props)
websites/staging/trafficserver/trunk/content/docs/v2/sdk/INKContDataSet.html (with props)
websites/staging/trafficserver/trunk/content/docs/v2/sdk/INKContDestroy.html (with props)
websites/staging/trafficserver/trunk/content/docs/v2/sdk/INKContMutexGet.html (with props)
websites/staging/trafficserver/trunk/content/docs/v2/sdk/INKContSchedule.html (with props)
websites/staging/trafficserver/trunk/content/docs/v2/sdk/INKError.html (with props)
websites/staging/trafficserver/trunk/content/docs/v2/sdk/INKHostLookupResultIPGet.html (with props)
websites/staging/trafficserver/trunk/content/docs/v2/sdk/INKHttpTxnServerIntercept.html (with props)
websites/staging/trafficserver/trunk/content/docs/v2/sdk/INKIOBufferBlockReadAvail.html (with props)
websites/staging/trafficserver/trunk/content/docs/v2/sdk/INKIOBufferBlockReadStart.html (with props)
websites/staging/trafficserver/trunk/content/docs/v2/sdk/INKIOBufferBlockWriteAvail.html (with props)
websites/staging/trafficserver/trunk/content/docs/v2/sdk/INKIOBufferBlockWriteStart.html (with props)
websites/staging/trafficserver/trunk/content/docs/v2/sdk/INKIOBufferCopy.html (with props)
websites/staging/trafficserver/trunk/content/docs/v2/sdk/INKIOBufferCreate.html (with props)
websites/staging/trafficserver/trunk/content/docs/v2/sdk/INKIOBufferDestroy.html (with props)
websites/staging/trafficserver/trunk/content/docs/v2/sdk/INKIOBufferProduce.html (with props)
websites/staging/trafficserver/trunk/content/docs/v2/sdk/INKIOBufferReaderAlloc.html (with props)
websites/staging/trafficserver/trunk/content/docs/v2/sdk/INKIOBufferReaderAvail.html (with props)
websites/staging/trafficserver/trunk/content/docs/v2/sdk/INKIOBufferReaderClone.html (with props)
websites/staging/trafficserver/trunk/content/docs/v2/sdk/INKIOBufferReaderConsume.html (with props)
websites/staging/trafficserver/trunk/content/docs/v2/sdk/INKIOBufferReaderFree.html (with props)
websites/staging/trafficserver/trunk/content/docs/v2/sdk/INKIOBufferReaderStart.html (with props)
websites/staging/trafficserver/trunk/content/docs/v2/sdk/INKIOBufferSizedCreate.html (with props)
websites/staging/trafficserver/trunk/content/docs/v2/sdk/INKIOBufferStart.html (with props)
websites/staging/trafficserver/trunk/content/docs/v2/sdk/INKIOBufferWaterMarkGet.html (with props)
websites/staging/trafficserver/trunk/content/docs/v2/sdk/INKIOBufferWaterMarkSet.html (with props)
websites/staging/trafficserver/trunk/content/docs/v2/sdk/INKIOBufferWrite.html (with props)
websites/staging/trafficserver/trunk/content/docs/v2/sdk/INKIsDebugTagSet.html (with props)
websites/staging/trafficserver/trunk/content/docs/v2/sdk/INKMBufferDestroy.html (with props)
websites/staging/trafficserver/trunk/content/docs/v2/sdk/INKMgmtFloatGet.html (with props)
websites/staging/trafficserver/trunk/content/docs/v2/sdk/INKMgmtIntGet.html (with props)
websites/staging/trafficserver/trunk/content/docs/v2/sdk/INKMgmtStringGet.html (with props)
websites/staging/trafficserver/trunk/content/docs/v2/sdk/INKMutexLock.html (with props)
websites/staging/trafficserver/trunk/content/docs/v2/sdk/INKMutexLockTry.html (with props)
websites/staging/trafficserver/trunk/content/docs/v2/sdk/INKMutexUnlock.html (with props)
websites/staging/trafficserver/trunk/content/docs/v2/sdk/INKNetConnect.html (with props)
websites/staging/trafficserver/trunk/content/docs/v2/sdk/INKNetVConnRemoteIPGet.html (with props)
websites/staging/trafficserver/trunk/content/docs/v2/sdk/INKNetVConnRemotePortGet.html (with props)
websites/staging/trafficserver/trunk/content/docs/v2/sdk/INKPluginDirGet.html (with props)
websites/staging/trafficserver/trunk/content/docs/v2/sdk/INKPluginLicenseRequired.html (with props)
websites/staging/trafficserver/trunk/content/docs/v2/sdk/INKPluginRegister.html (with props)
websites/staging/trafficserver/trunk/content/docs/v2/sdk/INKReleaseAssert.html (with props)
websites/staging/trafficserver/trunk/content/docs/v2/sdk/INKTextLogObjectDestroy.html (with props)
websites/staging/trafficserver/trunk/content/docs/v2/sdk/INKTextLogObjectFlush.html (with props)
websites/staging/trafficserver/trunk/content/docs/v2/sdk/INKTextLogObjectHeaderSet.html (with props)
websites/staging/trafficserver/trunk/content/docs/v2/sdk/INKTextLogObjectRollingEnabledSet.html (with props)
websites/staging/trafficserver/trunk/content/docs/v2/sdk/INKTextLogObjectRollingIntervalSecSet.html (with props)
websites/staging/trafficserver/trunk/content/docs/v2/sdk/INKTextLogObjectRollingOffsetHrSet.html (with props)
websites/staging/trafficserver/trunk/content/docs/v2/sdk/INKTextLogObjectWrite.html (with props)
websites/staging/trafficserver/trunk/content/docs/v2/sdk/INKThreadDestroy.html (with props)
websites/staging/trafficserver/trunk/content/docs/v2/sdk/INKThreadInit.html (with props)
websites/staging/trafficserver/trunk/content/docs/v2/sdk/INKThreadSelf.html (with props)
websites/staging/trafficserver/trunk/content/docs/v2/sdk/INKTrafficServerVersionGet.html (with props)
websites/staging/trafficserver/trunk/content/docs/v2/sdk/INKTransformOutputVConnGet.html (with props)
websites/staging/trafficserver/trunk/content/docs/v2/sdk/INKVConnCacheObjectSizeGet.html (with props)
websites/staging/trafficserver/trunk/content/docs/v2/sdk/INKVConnClose.html (with props)
websites/staging/trafficserver/trunk/content/docs/v2/sdk/INKVConnClosedGet.html (with props)
websites/staging/trafficserver/trunk/content/docs/v2/sdk/INKVConnRead.html (with props)
websites/staging/trafficserver/trunk/content/docs/v2/sdk/INKVConnReadVIOGet.html (with props)
websites/staging/trafficserver/trunk/content/docs/v2/sdk/INKVConnShutdown.html (with props)
websites/staging/trafficserver/trunk/content/docs/v2/sdk/INKVConnWrite.html (with props)
websites/staging/trafficserver/trunk/content/docs/v2/sdk/INKVConnWriteVIOGet.html (with props)
websites/staging/trafficserver/trunk/content/docs/v2/sdk/INKVIOContGet.html (with props)
websites/staging/trafficserver/trunk/content/docs/v2/sdk/INKVIOMutexGet.html (with props)
websites/staging/trafficserver/trunk/content/docs/v2/sdk/INKVIONBytesGet.html (with props)
websites/staging/trafficserver/trunk/content/docs/v2/sdk/INKVIONBytesSet.html (with props)
websites/staging/trafficserver/trunk/content/docs/v2/sdk/INKVIONDoneGet.html (with props)
websites/staging/trafficserver/trunk/content/docs/v2/sdk/INKVIONDoneSet.html (with props)
websites/staging/trafficserver/trunk/content/docs/v2/sdk/INKVIONTodoGet.html (with props)
websites/staging/trafficserver/trunk/content/docs/v2/sdk/INKVIOReaderGet.html (with props)
websites/staging/trafficserver/trunk/content/docs/v2/sdk/INKVIOReenable.html (with props)
websites/staging/trafficserver/trunk/content/docs/v2/sdk/INKVIOVConnGet.html (with props)
websites/staging/trafficserver/trunk/content/docs/v2/sdk/INKfflush.html (with props)
websites/staging/trafficserver/trunk/content/docs/v2/sdk/INKfgets.html (with props)
websites/staging/trafficserver/trunk/content/docs/v2/sdk/INKfopen.html (with props)
websites/staging/trafficserver/trunk/content/docs/v2/sdk/INKfopenFamily.html (with props)
websites/staging/trafficserver/trunk/content/docs/v2/sdk/INKfopenFamilyFunctions.html (with props)
websites/staging/trafficserver/trunk/content/docs/v2/sdk/INKfread.html (with props)
websites/staging/trafficserver/trunk/content/docs/v2/sdk/INKfwrite.html (with props)
websites/staging/trafficserver/trunk/content/docs/v2/sdk/INKmalloc.html (with props)
websites/staging/trafficserver/trunk/content/docs/v2/sdk/INKrealloc.html (with props)
websites/staging/trafficserver/trunk/content/docs/v2/sdk/INKstrdup.html (with props)
websites/staging/trafficserver/trunk/content/docs/v2/sdk/INKstrndup.html (with props)
websites/staging/trafficserver/trunk/content/docs/v2/sdk/IOBufferInterfaceFunctions.html (with props)
websites/staging/trafficserver/trunk/content/docs/v2/sdk/IOBuffers_IO.html (with props)
websites/staging/trafficserver/trunk/content/docs/v2/sdk/IOGuide.html (with props)
websites/staging/trafficserver/trunk/content/docs/v2/sdk/ImplementHandler_GetTransHandle.html (with props)
websites/staging/trafficserver/trunk/content/docs/v2/sdk/InitializationFunctions.html (with props)
websites/staging/trafficserver/trunk/content/docs/v2/sdk/InitiateConnectionFunctions.html (with props)
websites/staging/trafficserver/trunk/content/docs/v2/sdk/InitiateHTTPConnection.html (with props)
websites/staging/trafficserver/trunk/content/docs/v2/sdk/InterceptingHTTPTransactionFuncs.html (with props)
websites/staging/trafficserver/trunk/content/docs/v2/sdk/InterceptingHTTPTx.html (with props)
websites/staging/trafficserver/trunk/content/docs/v2/sdk/Interface_ThreadFunctions.html (with props)
websites/staging/trafficserver/trunk/content/docs/v2/sdk/LicensingPlugin.html (with props)
websites/staging/trafficserver/trunk/content/docs/v2/sdk/LoggingAPI.html (with props)
websites/staging/trafficserver/trunk/content/docs/v2/sdk/LoggingFunctions.html (with props)
websites/staging/trafficserver/trunk/content/docs/v2/sdk/MIMEFldsBelongAssocMIMEHdr.html (with props)
websites/staging/trafficserver/trunk/content/docs/v2/sdk/MIMEHeaders.html (with props)
websites/staging/trafficserver/trunk/content/docs/v2/sdk/ManagementInterfaceFunctions.html (with props)
websites/staging/trafficserver/trunk/content/docs/v2/sdk/MarshalBuffers.html (with props)
websites/staging/trafficserver/trunk/content/docs/v2/sdk/MarshallBuffersFunctions.html (with props)
websites/staging/trafficserver/trunk/content/docs/v2/sdk/MemoryAllocation.html (with props)
websites/staging/trafficserver/trunk/content/docs/v2/sdk/MemoryAllocationFunctions.html (with props)
websites/staging/trafficserver/trunk/content/docs/v2/sdk/MimeHeadersFunctions.html (with props)
websites/staging/trafficserver/trunk/content/docs/v2/sdk/MiscellaneousInterfaceGuide.html (with props)
websites/staging/trafficserver/trunk/content/docs/v2/sdk/MutexFunctions.html (with props)
websites/staging/trafficserver/trunk/content/docs/v2/sdk/MutexGuide.html (with props)
websites/staging/trafficserver/trunk/content/docs/v2/sdk/NamingConventions.html (with props)
websites/staging/trafficserver/trunk/content/docs/v2/sdk/NetVconnections.html (with props)
websites/staging/trafficserver/trunk/content/docs/v2/sdk/NetvconnectionFunctions.html (with props)
websites/staging/trafficserver/trunk/content/docs/v2/sdk/NewProtocolPlugins.html (with props)
websites/staging/trafficserver/trunk/content/docs/v2/sdk/OtherDeprecatedFunctions.html (with props)
websites/staging/trafficserver/trunk/content/docs/v2/sdk/PluginConfigurationFunctions.html (with props)
websites/staging/trafficserver/trunk/content/docs/v2/sdk/PluginConfigurations.html (with props)
websites/staging/trafficserver/trunk/content/docs/v2/sdk/PluginManagement.html (with props)
websites/staging/trafficserver/trunk/content/docs/v2/sdk/PlusingRegisAndVersionCkg.html (with props)
websites/staging/trafficserver/trunk/content/docs/v2/sdk/Preface.html (with props)
websites/staging/trafficserver/trunk/content/docs/v2/sdk/ReadTESettingStats.html (with props)
websites/staging/trafficserver/trunk/content/docs/v2/sdk/RemapAPI_Example.html (with props)
websites/staging/trafficserver/trunk/content/docs/v2/sdk/RestartingTS.html (with props)
websites/staging/trafficserver/trunk/content/docs/v2/sdk/RlsMarshalBufHandles.html (with props)
websites/staging/trafficserver/trunk/content/docs/v2/sdk/Roadmap_CreatingPlugins.html (with props)
websites/staging/trafficserver/trunk/content/docs/v2/sdk/SampleBufferedNullTransformPlugin.html (with props)
websites/staging/trafficserver/trunk/content/docs/v2/sdk/SampleNullTransformPlugin.html (with props)
websites/staging/trafficserver/trunk/content/docs/v2/sdk/SetTransactionHook.html (with props)
websites/staging/trafficserver/trunk/content/docs/v2/sdk/SetUpLicensing.html (with props)
websites/staging/trafficserver/trunk/content/docs/v2/sdk/SettingGlobalHook.html (with props)
websites/staging/trafficserver/trunk/content/docs/v2/sdk/SettingUpTransacHook.html (with props)
websites/staging/trafficserver/trunk/content/docs/v2/sdk/SettingUpUIUpdateCallbacks.html (with props)
websites/staging/trafficserver/trunk/content/docs/v2/sdk/SpecifyingPluginLocation.html (with props)
websites/staging/trafficserver/trunk/content/docs/v2/sdk/StatisticsFunctions.html (with props)
websites/staging/trafficserver/trunk/content/docs/v2/sdk/TEConfigReadFunctions.html (with props)
websites/staging/trafficserver/trunk/content/docs/v2/sdk/ThreadFunctions.html (with props)
websites/staging/trafficserver/trunk/content/docs/v2/sdk/TransformationFunctions.html (with props)
websites/staging/trafficserver/trunk/content/docs/v2/sdk/Transformations_IO.html (with props)
websites/staging/trafficserver/trunk/content/docs/v2/sdk/Trouble_DebugMemLeaks.html (with props)
websites/staging/trafficserver/trunk/content/docs/v2/sdk/Trouble_DebugTags.html (with props)
websites/staging/trafficserver/trunk/content/docs/v2/sdk/Trouble_LoadPlugins.html (with props)
websites/staging/trafficserver/trunk/content/docs/v2/sdk/Trouble_UsingDebugger.html (with props)
websites/staging/trafficserver/trunk/content/docs/v2/sdk/TypeIndex.html (with props)
websites/staging/trafficserver/trunk/content/docs/v2/sdk/URLFunctions.html (with props)
websites/staging/trafficserver/trunk/content/docs/v2/sdk/URLs.html (with props)
websites/staging/trafficserver/trunk/content/docs/v2/sdk/Updatingplugin.configFile.html (with props)
websites/staging/trafficserver/trunk/content/docs/v2/sdk/VIOFunctions.html (with props)
websites/staging/trafficserver/trunk/content/docs/v2/sdk/VIOs_IO.html (with props)
websites/staging/trafficserver/trunk/content/docs/v2/sdk/VconnectionFunctions.html (with props)
websites/staging/trafficserver/trunk/content/docs/v2/sdk/ViewStatsUsingTrafLine.html (with props)
websites/staging/trafficserver/trunk/content/docs/v2/sdk/WorkWHTTPHeaderFunc.html (with props)
websites/staging/trafficserver/trunk/content/docs/v2/sdk/WorkWithHTTPHeaders.html (with props)
websites/staging/trafficserver/trunk/content/docs/v2/sdk/WritingHandlerFunctions.html (with props)
websites/staging/trafficserver/trunk/content/docs/v2/sdk/ch03.html (with props)
websites/staging/trafficserver/trunk/content/docs/v2/sdk/ch03s02.html (with props)
websites/staging/trafficserver/trunk/content/docs/v2/sdk/ch03s03.html (with props)
websites/staging/trafficserver/trunk/content/docs/v2/sdk/ch03s04.html (with props)
websites/staging/trafficserver/trunk/content/docs/v2/sdk/ch07.html (with props)
websites/staging/trafficserver/trunk/content/docs/v2/sdk/ch07s02.html (with props)
websites/staging/trafficserver/trunk/content/docs/v2/sdk/ch07s03.html (with props)
websites/staging/trafficserver/trunk/content/docs/v2/sdk/ch07s04.html (with props)
websites/staging/trafficserver/trunk/content/docs/v2/sdk/ch07s05.html (with props)
websites/staging/trafficserver/trunk/content/docs/v2/sdk/ch18s09s04.html (with props)
websites/staging/trafficserver/trunk/content/docs/v2/sdk/css/
websites/staging/trafficserver/trunk/content/docs/v2/sdk/css/ydoc.css
websites/staging/trafficserver/trunk/content/docs/v2/sdk/images/
websites/staging/trafficserver/trunk/content/docs/v2/sdk/images/Protocol_state_diagram.jpg (with props)
websites/staging/trafficserver/trunk/content/docs/v2/sdk/images/Uses.jpg (with props)
websites/staging/trafficserver/trunk/content/docs/v2/sdk/images/blacklist75.jpg (with props)
websites/staging/trafficserver/trunk/content/docs/v2/sdk/images/docbook/
websites/staging/trafficserver/trunk/content/docs/v2/sdk/images/docbook/caution.png (with props)
websites/staging/trafficserver/trunk/content/docs/v2/sdk/images/docbook/important.png (with props)
websites/staging/trafficserver/trunk/content/docs/v2/sdk/images/docbook/note.png (with props)
websites/staging/trafficserver/trunk/content/docs/v2/sdk/images/docbook/tip.png (with props)
websites/staging/trafficserver/trunk/content/docs/v2/sdk/images/docbook/ts75.png (with props)
websites/staging/trafficserver/trunk/content/docs/v2/sdk/images/event_sys80.jpg (with props)
websites/staging/trafficserver/trunk/content/docs/v2/sdk/images/evt_plugin120.jpg (with props)
websites/staging/trafficserver/trunk/content/docs/v2/sdk/images/http_header_struct.jpg (with props)
websites/staging/trafficserver/trunk/content/docs/v2/sdk/images/http_headers.jpg (with props)
websites/staging/trafficserver/trunk/content/docs/v2/sdk/images/http_state2.jpg (with props)
websites/staging/trafficserver/trunk/content/docs/v2/sdk/images/marshall_buffers.jpg (with props)
websites/staging/trafficserver/trunk/content/docs/v2/sdk/images/plugin_process.jpg (with props)
websites/staging/trafficserver/trunk/content/docs/v2/sdk/images/protocol_evt.jpg (with props)
websites/staging/trafficserver/trunk/content/docs/v2/sdk/images/protocol_sm_big.jpg (with props)
websites/staging/trafficserver/trunk/content/docs/v2/sdk/images/transact75.jpg (with props)
websites/staging/trafficserver/trunk/content/docs/v2/sdk/images/transact_hook75.jpg (with props)
websites/staging/trafficserver/trunk/content/docs/v2/sdk/images/txn_sm.jpg (with props)
websites/staging/trafficserver/trunk/content/docs/v2/sdk/images/vconn_buf_output.jpg (with props)
websites/staging/trafficserver/trunk/content/docs/v2/sdk/images/vconn_buffer.jpg (with props)
websites/staging/trafficserver/trunk/content/docs/v2/sdk/images/vconnection.jpg (with props)
websites/staging/trafficserver/trunk/content/docs/v2/sdk/images/vconnection1.jpg (with props)
websites/staging/trafficserver/trunk/content/docs/v2/sdk/images/vconnection2.jpg (with props)
websites/staging/trafficserver/trunk/content/docs/v2/sdk/index.html (with props)
websites/staging/trafficserver/trunk/content/docs/v2/sdk/js/
websites/staging/trafficserver/trunk/content/docs/v2/sdk/js/tocnodes.js
websites/staging/trafficserver/trunk/content/docs/v2/sdk/pr01s02.html (with props)
websites/staging/trafficserver/trunk/content/docs/v2/sdk/sdk_1_5_deprecated.pdf (with props)
websites/staging/trafficserver/trunk/content/docs/v2/sdk/top.html (with props)
websites/staging/trafficserver/trunk/content/docs/v2/search.html (with props)
websites/staging/trafficserver/trunk/content/docs/v2/top.html (with props)
Added: websites/staging/trafficserver/trunk/content/docs/v2/.htaccess
==============================================================================
--- websites/staging/trafficserver/trunk/content/docs/v2/.htaccess (added)
+++ websites/staging/trafficserver/trunk/content/docs/v2/.htaccess Mon Dec 19 22:58:01 2011
@@ -0,0 +1,3 @@
+RedirectPermanent /docs/v2/index.html /docs/
+Options +Includes
+XBitHack on
Added: websites/staging/trafficserver/trunk/content/docs/v2/admin/Glossary.htm
==============================================================================
--- websites/staging/trafficserver/trunk/content/docs/v2/admin/Glossary.htm (added)
+++ websites/staging/trafficserver/trunk/content/docs/v2/admin/Glossary.htm Mon Dec 19 22:58:01 2011
@@ -0,0 +1,230 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">
+<html>
+<head>
+<title>Traffic Server Administrator's Guide Glossary</title>
+
+<!--#include file="top.html" -->
+
+ <h1>
+ <a name="561">Glossary</a> </h1>
+<dl>
+ <dt><a name="932"><strong>alternates</strong></a></dt>
+ <dd>Different versions of the same web object. Some origin servers answer requests to the same URL with a variety of objects. The content of these objects can vary widely, depending on whether a server delivers content for different languages, targets different browsers with different presentation styles, or delivers variable content at different times of the day. </dd>
+<dt><strong><a name="633">cache</a></strong>
+</dt>
+<dd>Stores copies of frequently-accessed objects close to users and serves them to users when requested. Also see: <a href="#3058">object store</a>.</dd>
+<dt><strong><a name="3357">cache hierarchy</a></strong>
+</dt>
+<dd>Cache levels that communicate with each other. All cache hierarchies recognize the concepts of <a href="#2326">parent cache</a> and <a href="#3158">child cache</a>.</dd>
+<dt><strong><a name="3407">cache hit</a></strong>
+</dt>
+<dd>An object in the cache that can be served directly to the client.</dd>
+<dt><strong><a name="3409">cache miss</a></strong>
+</dt>
+<dd>An object that is <em>not</em> in the cache or that is in the cache but no longer valid. In both cases, Traffic Server must retrieve the object from the <a href="#2215">origin server</a>.</dd>
+<dt><strong><a name="2810">caching web proxy server</a></strong>
+</dt>
+<dd>A web proxy server with local cache storage that allows the proxy to fulfill client requests locally, using a cached copy of the origin serverâs previous response.</dd>
+<dt><strong><a name="3109">CGI </a></strong>
+</dt>
+<dd>Common Gateway Interface. A set of rules that describe how an origin server and another piece of software (a CGI program) located on the same machine communicate.</dd>
+<dt><strong><a name="3157">cgi-bin</a></strong>
+</dt>
+<dd>The most common directory name on an origin server in which <a href="#3109">CGI</a> programs are stored.</dd>
+<dt><strong><a name="3158">child cache</a></strong>
+</dt>
+<dd>A cache lower in a <a href="#3357">cache hierarchy</a> for which Traffic Server is a parent; child and parent communicate directly. See also: <a href="#2326">parent cache</a>.</dd>
+<dt><strong><a name="2219">cluster</a></strong>
+</dt>
+<dd>A group of Traffic Server nodes that share configuration information and can act as a single large virtual cache.</dd>
+<dt><strong><a name="2419">cookie</a></strong>
+</dt>
+<dd>A piece of information sent by an origin server to a web browser. The browser software saves the information and sends it back to the server whenever the browser makes additional requests from the server. Cookies enable origin servers to keep track of users.</dd>
+
+<dt> <strong><a name="2274">DNS</a></strong>
+</dt>
+ <dd>Domain Name Service. Traffic Server includes a fast, asynchronous DNS resolver to streamline conversion of hostnames to IP addresses. </dd>
+ <dt>
+ <strong><a name="2205">explicit proxy caching</a></strong>
+ </dt>
+ <dd>A Traffic Server configuration option, in which client software (typically a browser) must be specifically configured to send web requests to the Traffic Server proxy.</dd>
+ <dt>
+ <strong><a name="4092">forward proxy caching</a></strong>
+ </dt>
+ <dd>Proxy caching of content requested by web clients. Can be <b>transparent</b> or <a href="#2205">explicit</a>. </dd>
+ <dt>
+ <strong><a name="3052">full clustering</a></strong>
+ </dt>
+ <dd>A Traffic Server cluster that distributes its cache across its nodes into a single, virtual object store, rather than replicating the cache node-by-node. See also: <a href="#3050">management-only clustering</a>. </dd>
+ <dt>
+ <strong><a name="3908">hierarchical live splitting</a></strong> </dt>
+ <dd>When a hierarchical deployment for streaming media performs live splitting. See also: <a href="#3923">hierarchy</a> and <a href="#3941">live splitting</a>. </dd>
+ <dt>
+ <strong><a name="3923">hierarchy</a></strong>
+ </dt>
+ <dd>Two or more Traffic Server hosts between the client and the content. One host between the client and the content is a <b>single-level hierarchy</b>. </dd>
+ <dt>
+ <strong><a name="573">HTTP</a></strong>
+ </dt>
+ <dd>Hypertext Transfer Protocol. The client/server protocol upon which the World Wide Web is based. </dd>
+ <dt>
+ <strong><a name="2169">ICP</a></strong>
+ </dt>
+ <dd>Internet Cache Protocol. A protocol for proxy caches to exchange information about their content. </dd>
+ <dt>
+ <strong><a name="2270">IP</a></strong>
+ </dt>
+ <dd>Internet Protocol. The lowest-layer protocol under TCP/IP, responsible for end-to-end forwarding and long packet fragmentation control. </dd>
+ <dt>
+ <strong><a name="2272">ISP</a></strong>
+ </dt>
+ <dd>Internet Service Provider. An organization that provides access to the Internet. </dd>
+ <dt>
+ <strong><a name="3105">JavaScript</a></strong>
+ </dt>
+ <dd>
+ <a name="5667">A scripting language commonly used to create </a>web pages. JavaScript is used to make web pages more interactive (such as to display forms and buttons). JavaScript can be used with Java, but Java is not required for JavaScript to work correctly.
+ </dd>
+ <dt>
+ <strong><a name="2783">L4 switch</a></strong>
+ </dt>
+ <dd>An Ethernet switch that controls network traffic flow using Level 4 rules. The switch can intercept desired client protocol packets and direct them to a proxy for transparent operation. </dd>
+ <dt>
+ <strong><a name="3954">live passthrough mode</a></strong>
+ </dt>
+ <dd>The phrase used to describe when Traffic Server passes live streams from the origin server to the client. </dd>
+ <dt>
+ <strong><a name="3941">live splitting</a></strong>
+ </dt>
+ <dd>Occurs when Traffic Server splits one live stream from the origin server into several streams to different clients. </dd>
+ <dt>
+ <strong><a name="3050">management-only clustering</a></strong>
+ </dt>
+ <dd>A Traffic Server option wherein all nodes in a cluster automatically share configuration information. See also: <a href="#3052">full clustering</a>. </dd>
+ <dt>
+ <strong><a name="2286">Netscape log format</a></strong>
+ </dt>
+ <dd>A standard access log format. Using the Netscape log format, you can analyze Traffic Server access log files with off-the-shelf log analysis scripts. See also: <a href="#2175">Squid log format</a>.</dd>
+ <dt>
+ <strong><a name="3107">news server</a></strong>
+ </dt>
+ <dd>
+ <a name="3108">A server that controls access to a news group. To read and post messages to a news group, a </a>user must connect to a news server.
+ </dd>
+ <dt>
+ <strong><a name="2165">NNTP</a></strong>
+ </dt>
+ <dd>Network News Transfer Protocol. A protocol used to distribute, inquire, retrieve, and post news articles. </dd>
+ <dt>
+ <strong><a name="3058">object store</a></strong>
+ </dt>
+ <dd>A custom high-speed database on which Traffic Server stores all cached objects. </dd>
+ <dt>
+ <strong><a name="2215">origin server</a></strong>
+ </dt>
+ <dd>The web server that contains the original copy of the requested information. </dd>
+ <dt>
+ <strong><a name="3630">PAC file</a></strong>
+ </dt>
+ <dd>Proxy Auto-Configuration file. A specialized JavaScript function definition that a browser calls to determine how requests are handled. </dd>
+ <dt>
+ <strong><a name="2326">parent cache</a></strong>
+ </dt>
+ <dd>A cache higher up in a <a href="#3357">cache hierarchy</a> to which Traffic Server can send requests. </dd>
+ <dt>
+ <strong><a name="2324">plugin</a></strong>
+ </dt>
+ <dd>An add-on feature that provides additional functionality to Traffic Server, such as origin server blacklisting, web content filtering, authentication, and data transformation. </dd>
+ <dt>
+ <strong><a name="2195">proxy server</a></strong>
+ </dt>
+ <dd>See <a href="#2191">web proxy server</a>. </dd>
+ <dt>
+ <strong><a name="3997">pull splitting</a></strong>
+ </dt>
+ <dd>Occurs when a host contacts the upstream host to send payload data. </dd>
+ <dt>
+ <strong><a name="4006">push splitting</a></strong>
+ </dt>
+ <dd>Occurs when an upstream host sends data to the downstream host with no request from the downstream host. </dd>
+ <dt>
+ <strong><a name="2452">reverse proxy</a></strong>
+ </dt>
+ <dd>A option that enables Traffic Server to be configured as an origin server for convenient geographical distribution of server content. Reverse proxy also offloads static content service from servers that build dynamic content and provides a peak load buffer (or <b>surge protector</b>) for origin servers. Sometimes referred to as <a href="#2183">server acceleration</a>. </dd>
+ <dt>
+ <strong><a name="3196">router</a></strong> </dt>
+ <dd>A device that handles the connection between two or more networks. Routers look at the destination addresses of the packets passing through them and decide which route to send them on. </dd>
+ <dt>
+ <strong><a name="2183">server acceleration</a></strong> </dt>
+ <dd>See <a href="#2452">reverse proxy</a>. </dd>
+ <dt>
+ <strong><a name="2531">SOCKS</a></strong>
+ </dt>
+ <dd>A circuit-level proxy protocol that provides a tunneling mechanism for protocols that cannot be proxied conveniently. </dd>
+ <dt>
+ <strong><a name="2175">Squid log format</a></strong>
+ </dt>
+ <dd>A standard access log format. With the Squid log format, you can analyze Traffic Server event log files with off-the-shelf log analysis scripts. See also: <a href="#2286">Netscape log format</a>. </dd>
+ <dt>
+ <strong><a name="2308">SSL</a></strong>
+ </dt>
+ <dd>Secure Sockets Layer. A protocol that enables encrypted, authenticated communications across the Internet. SSL is used mostly in communications between origin servers and web browsers. </dd>
+ <dt>
+ <strong><a name="2284">syslog</a></strong>
+ </dt>
+ <dd>The UNIX system logging facility. </dd>
+ <dt>
+ <strong><a name="2181">TCP</a></strong>
+ </dt>
+ <dd>Transmission Control Protocol. An Internet Standard transport layer protocol that provides reliable end-to-end communication by using sequenced data sent by IP. </dd>
+ <dt>
+ <strong><a name="2283">traffic_cop</a></strong>
+ </dt>
+ <dd>A Traffic Server process that periodically monitors the health of the <a href="#2984">traffic_server</a> and <a href="#2976">traffic_manager</a> processes by issuing heartbeat requests to fetch synthetic web pages. </dd>
+ <dt>
+ <strong><a name="2179">Traffic Line</a></strong>
+ </dt>
+ <dd>A Traffic Server command-line utility that enables you to monitor performance and change configuration settings. </dd>
+ <dt>
+ <strong><a name="2976">traffic_manager</a></strong>
+ </dt>
+ <dd>The Traffic Server process responsible for launching, monitoring, and reconfiguring the <a href="#2984">traffic_server</a> process. It is also responsible for the proxy autoconfiguration port, cluster administration, and <a href="#2268">virtual IP failover</a>. </dd>
+ <dt>
+ <strong><a name="2984">traffic_server</a></strong>
+ </dt>
+ <dd>A Traffic Server process that is the cache processing engine of the Traffic Server product. <code>traffic_server</code> is responsible for accepting connections, processing requests, and serving documents from the <a href="#633">cache</a> or <a href="#2215">origin server</a>. </dd>
+ <dt>
+ <strong><a name="2185">Traffic Shell</a></strong>
+ </dt>
+ <dd>A Traffic Server command-line tool that enables you to monitor performance and change configuration settings. </dd>
+ <dt>
+ <strong><a name="4128">UDP</a></strong>
+ </dt>
+ <dd>User Datagram Protocol. The underlying transport protocol used by the data transfer protocols. </dd>
+ <dt>
+ <strong><a name="4130">Underlying transport protocol</a></strong>
+ </dt>
+ <dd>A protocol that transports bits. See also: <a href="#3854">Control Protocol</a> and <a href="#5730">Data Transfer Protocol</a>. </dd>
+ <dt>
+ <strong><a name="2276">URL</a></strong>
+ </dt>
+ <dd>Uniform Resource Locator. The address that defines the route to a file on the web or other Internet facility. </dd>
+ <dt>
+ <strong><a name="2268">virtual IP failover</a></strong>
+ </dt>
+ <dd>An option available to clustered Traffic Servers, in which Traffic Server maintains a pool of virtual IP addresses that it assigns to the nodes of a cluster. If a node fails, then the remaining nodes mask the fault and take over the failed nodeâs virtual interface. </dd>
+ <dt>
+ <strong><a name="2191">web proxy server</a></strong>
+ </dt>
+ <dd>A web server that forwards client requests to <a href="#2215">origin server</a>s. The proxy server can deny requests according to filter rules or security limitations. </dd>
+ <dt>
+ <strong><a name="2132">web server</a></strong>
+ </dt>
+ <dd>A computer that provides World Wide Web services on the Internet. See also: <a href="#2215">origin server</a>. </dd>
+ <dt>
+ <strong><a name="2788">WPAD</a></strong>
+ </dt>
+ <dd>Web Proxy Auto-Discovery. A protocol that allows clients to automatically locate a web proxy, providing the benefits of a proxy without the need for explicit client configuration. </dd>
+</dl>
+
+<!--#include file="bottom.html" -->
\ No newline at end of file
Propchange: websites/staging/trafficserver/trunk/content/docs/v2/admin/Glossary.htm
------------------------------------------------------------------------------
svn:executable = *
Added: websites/staging/trafficserver/trunk/content/docs/v2/admin/TE_Admin_v1_5_deprecated.pdf
==============================================================================
Binary file - no diff available.
Propchange: websites/staging/trafficserver/trunk/content/docs/v2/admin/TE_Admin_v1_5_deprecated.pdf
------------------------------------------------------------------------------
svn:mime-type = application/octet-stream
Added: websites/staging/trafficserver/trunk/content/docs/v2/admin/bottom.html
==============================================================================
--- websites/staging/trafficserver/trunk/content/docs/v2/admin/bottom.html (added)
+++ websites/staging/trafficserver/trunk/content/docs/v2/admin/bottom.html Mon Dec 19 22:58:01 2011
@@ -0,0 +1,30 @@
+ </div>
+ </div>
+ </div>
+ <div role="navigation" class="yui-b">
+ <ul class="leftnav">
+ <li><a href="intro.htm">Overview</a></li>
+ <li><a href="getstart.htm">Getting Started</a></li>
+ <li><a href="http.htm">HTTP Proxy Caching </a></li>
+ <li><a href="explicit.htm">Explicit Proxy Caching</a></li>
+ <li><a href="reverse.htm">Reverse Proxy and HTTP Redirects</a></li>
+ <li><a href="hier.htm">Hierarchical Caching</a></li>
+ <li><a href="cache.htm">Configuring the Cache</a></li>
+ <li><a href="monitor.htm">Monitoring Traffic</a></li>
+ <li><a href="configure.htm">Configuring Traffic Server</a></li>
+ <li><a href="secure.htm">Security Options</a></li>
+ <li><a href="log.htm">Working with Log Files</a></li>
+ <li><a href="cli.htm">Traffic Line Commands</a></li>
+ <li><a href="logfmts.htm">Event Logging Formats</a></li>
+ <li><a href="files.htm">Configuration Files</a> </li>
+ <li><a href="errors.htm">Traffic Server Error Messages</a></li>
+ <li><a href="trouble.htm">FAQ and Troubleshooting Tips</a></li>
+ <li><a href="ts_admin_chinese.pdf">Traffic Server 管çåæå</a> (PDF)</li>
+ </ul>
+ </div>
+ </div>
+ <div id="ft" role="contentinfo">
+ Copyright © <!--#config timefmt="%Y"--> <!--#echo var="DATE_LOCAL" --> <a href="http://www.apache.org/">The Apache Software Foundation</a>. Licensed under the <a href="http://www.apache.org/licenses/">Apache License</a>, Version 2.0. Apache Traffic Server, Apache, the Apache Traffic Server logo, and the Apache feather logo are trademarks of The Apache Software Foundation.</div>
+</div>
+</body>
+</html>
Propchange: websites/staging/trafficserver/trunk/content/docs/v2/admin/bottom.html
------------------------------------------------------------------------------
svn:executable = *
Added: websites/staging/trafficserver/trunk/content/docs/v2/admin/cache.htm
==============================================================================
--- websites/staging/trafficserver/trunk/content/docs/v2/admin/cache.htm (added)
+++ websites/staging/trafficserver/trunk/content/docs/v2/admin/cache.htm Mon Dec 19 22:58:01 2011
@@ -0,0 +1,187 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">
+<html>
+<head>
+<title>Traffic Edge Administrator's Guide</title>
+
+<!--#include file="top.html" -->
+
+<h1>Configuring the Cache</h1>
+<p>The Traffic Server cache consists of a high-speed object database called the <b>object store </b>that indexes objects according to URLs and their associated headers.</p>
+<p>This chapter discusses the following topics: </p>
+<ul>
+<li><a href="#TrafficEdgeCache">The Traffic Server Cache</a></li>
+<li><a href="#RAMCache">The RAM Cache</a></li>
+<li><a href="#ChangingSizeRAMCache">Changing the Size of the RAM Cache</a></li>
+<li><a href="#ChangingCacheCapacity">Changing Cache Capacity</a></li>
+<li><a href="#PartitioningCache">Partitioning the Cache</a></li>
+<li><a href="#ConfiguringCacheObjectSizeLimit">Configuring the Cache Object Size Limit</a></li>
+<li><a href="#ClearingCache">Clearing the Cache</a></li>
+<li><a href="#RemoveObjectFromCache">Removing an Object From the Cache</a></li>
+<li><a href="#InspectingCache">Inspecting the Cache</a></li>
+</ul>
+<h2 id="TrafficEdgeCache">The Traffic Server Cache</h2>
+<p>The Traffic Server cache consists of a high-speed object database called the <b>object store</b>. The object store indexes objects according to URLs and associated headers. This enables Traffic Server to store, retrieve, and serve not only web pages, but also parts of web pages - which provides optimum bandwidth savings. Using sophisticated object management, the object store can cache alternate versions of the same object (versions may differ because of dissimilar language or encoding types). It can also efficiently store very small and very large documents, thereby minimizing wasted space. When the cache is full, Traffic Server removes stale data to ensure the most requested objects are kept readily available and fresh. </p>
+<p>Traffic Server is designed to tolerate total disk failures on any of the cache disks. If the disk fails completely, then Traffic Server marks the entire disk as corrupt and continues using the remaining disks. An alarm is then created to indicate which disk failed. If all of the cache disks fail, then Traffic Server goes into proxy-only mode. </p>
+<p>You can perform the following cache configuration tasks: </p>
+<ul>
+ <li>Change the total amount of disk space allocated to the cache: refer to <a href="#ChangingCacheCapacity">Changing Cache Capacity</a>. </li>
+ <li>Partition the cache by reserving cache disk space for specific protocols and origin servers/domains: refer to <a href="#PartitioningCache">Partitioning the Cache</a>. </li>
+ <li>Delete all data in the cache: refer to <a href="#ClearingCache">Clearing the Cache</a>.</li>
+</ul>
+<h2 id="RAMCache">The RAM Cache</h2>
+<p>Traffic Server maintains a small RAM cache of extremely popular objects. This RAM cache serves the most popular objects as quickly as possible and reduces load on disks, especially during temporary traffic peaks. You can configure the RAM cache size to suit your needs, as described in <a href="#ChangingSizeRAMCache">Changing the Size of the RAM Cache</a> below. </p>
+<h2 id="ChangingSizeRAMCache">Changing the Size of the RAM Cache</h2>
+<p>Traffic Server provides a dedicated RAM cache for fast retrieval of popular small objects. The default RAM cache size is automatically calculated based on the number and size of the cache partitions you have configured. If you've partitioned your cache according to protocol and/or hosts, then the size of the RAM cache for each partition is proportional to the size of that partition. </p>
+<p>You can increase the RAM cache size for better cache hit performance. However, if you increase the size of the RAM cache and observe a decrease in performance (such as increased latencies), then it's possible that the operating system requires more memory for network resources. In such instances, you should return the RAM cache size to its previous value.</p>
+<h5>To change the RAM cache size: </h5>
+<ol>
+ <li>Stop Traffic Server. </li>
+ <li>In a text editor, open the <code>records.config</code> file located in the Traffic Server <code>config</code> directory. </li>
+ <li>Edit the following variable:</li>
+
+
+<table width="1232" border="1">
+ <tr>
+ <th width="322" scope="col">Variable</th>
+ <th width="894" scope="col">Description</th>
+ </tr>
+ <tr>
+ <td><i><code>proxy.config.cache.ram_cache.size</code></i></td>
+ <td>Set this variable to specify the size of the RAM cache.<br />
+ The default value of -1 means that the RAM cache is automatically sized at approximately 1MB per gigabyte of disk.</td>
+ </tr>
+</table>
+
+
+ <li>Save and close the <code>records.config</code> file. </li>
+ <li>Restart Traffic Server. If you increase the RAM cache to a size or 1GB or more, then restart with the <code>start_traffic_server</code> command (refer to <a href="getstart.htm#StartingTrafficEdge">Starting Traffic Server</a>). </li>
+</ol>
+<p> </p>
+<h2 id="ChangingCacheCapacity">Changing Cache Capacity</h2>
+<p>You can increase or reduce the total amount of disk space allocated to the cache without clearing the content. To check the size of the cache (in bytes), enter the command <code>traffic_line -r proxy.process.cache.bytes_total</code>. </p>
+<h3>Increasing Cache Capacity </h3>
+<p>To increase the total amount of disk space allocated to the cache on existing disks or to add new disks to a Traffic Server node, follow the steps below:</p>
+<ol>
+ <li>Stop Traffic Server. </li>
+ <li>Add hardware, if necessary. </li>
+ <li>Edit the Traffic Server <code>storage.config</code> file: increase the amount of disk space allocated to the cache on existing disks or describe the new hardware you are adding (refer to <a href="files.htm#storage.config">storage.config</a>).</li>
+ <li>If you add a new disk, then you must edit the <code>/etc/rc.d/init.d/traffic_server</code> file to add a raw disk binding. Instructions for adding a raw disk binding are located in the Traffic Server <code>storage.config</code> file. </li>
+ <li>Restart Traffic Server. </li>
+</ol>
+<h3>Reducing Cache Capacity </h3>
+<p>To reduce the total amount of disk space allocated to the cache on an existing disk or to remove disks from a Traffic Server node, follow the steps below:</p>
+<ol>
+ <li>Stop Traffic Server. </li>
+ <li>Remove hardware, if necessary. </li>
+ <li>Edit the Traffic Server <code>storage.config</code> file: reduce the amount of disk space allocated to the cache on existing disks or delete the reference to the hardware you're removing (refer to <a href="files.htm#storage.config">storage.config</a>). </li>
+ <li>If you remove a disk, then you must edit the <code>/etc/rc.d/init.d/traffic_server</code> file to remove the raw disk binding for the disk. </li>
+ <li>Restart Traffic Server. </li>
+</ol>
+<p><strong>IMPORTANT:</strong> In the <code>storage.config</code> file, a formatted or raw disk must be at least 128 MB. </p>
+<h2 id="PartitioningCache">Partitioning the Cache</h2>
+<p>You can manage your cache space more efficiently and restrict disk usage by creating cache partitions with different sizes for specific protocols. You can further configure these partitions to store data from specific origin servers and/or domains. The partition configuration must be the same on all nodes in a cluster. </p>
+<h3 id="CreatingCachePartitionsSpecificProtocols">Creating Cache Partitions for Specific Protocols</h3>
+<p>You can create separate partitions for your cache that vary in size to store content according to protocol. This ensures that a certain amount of disk space is always available for a particular protocol. Traffic Server currently supports the <b>http</b> partition type for HTTP objects.</p>
+<h5>To partition the cache according to protocol: </h5>
+<ol>
+ <li>In a text editor, open the <code>partition.config</code> file located in the Traffic Server <code>config</code> directory. </li>
+ <li>Enter a line in the file for each partition you want to create (refer to <a href="files.htm#partition.config">partition.config</a>). </li>
+ <li>Save and close the <code>partition.config</code> file. </li>
+ <li>Restart Traffic Server. </li>
+</ol>
+<h4>Making Changes to Partition Sizes and Protocols </h4>
+<p>After you've configured your cache partitions based on protocol, you can make changes to the configuration at any time. Before making changes, note the following: </p>
+<ul>
+ <li>You must stop Traffic Server before you change the cache partition size and protocol assignment. </li>
+ <li>When you increase the size of a partition, the contents of the partition are <em>not</em> deleted However, when you reduce the size of a partition, the contents of the partition <em>are</em> deleted. </li>
+ <li>When you change the partition number, the partition is deleted and then recreated, even if the size and protocol type remain the same. </li>
+ <li>When you add new disks to your Traffic Server node, partition sizes specified in percentages will increase proportionately. </li>
+ <li>A lot of changes to partition sizes might result in disk fragmentation, which affects performance and hit rate. You should clear the cache before making many changes to cache partition sizes (refer to <a href="#ClearingCache">Clearing the Cache</a>).</li>
+</ul>
+<h3>Partitioning the Cache According to Origin Server or Domain</h3>
+<p>After you have partitioned the cache according to size and protocol, you can assign the partitions you created to specific origin servers and/or domains. You can assign a partition to a single origin server or to multiple origin servers. However, if a partition is assigned to multiple origin servers, then there is no guarantee on the space available in the partition for each origin server. Content is stored in the partition according to popularity. In addition to assigning partitions to specific origin servers and domains, you must assign a generic partition to store content from all origin servers and domains that are not listed. This generic partition is also used if the partitions for a particular origin server or domain become corrupt. If you do not assign a generic partition, then Traffic Server will run in proxy-only mode. </p>
+<p><strong>Note: </strong>You do <em>not</em> need to stop Traffic Server before you assign partitions to particular hosts or domains. However, this type of configuration is time-consuming and can cause a spike in memory usage. Therefore, it's best to configure partition assignment during periods of low traffic. </p>
+<h5>To partition the cache according to hostname and domain: </h5>
+<ol>
+ <li>Configure the cache partitions according to size and protocol, as described in <a href="#CreatingCachePartitionsSpecificProtocols">Creating Cache Partitions for Specific Protocols</a>. </li>
+ <li>Create a separate partition based on protocol for each host and domain, as well as an additional generic partition to use for content that does not belong to these origin servers or domains. The partitions do not need to be the same size. </li>
+ <li>In a text editor, open the <code>hosting.config</code> file located in the Traffic Server <code>config</code> directory. </li>
+ <li>Enter a line in the file to allocate the partition(s) used for each origin server and/or domain (refer to <a href="files.htm#hosting.config">hosting.config</a>). </li>
+ <li>Assign a generic partition to use for content that does not belong to any of the origin servers or domains listed in the file. If all partitions for a particular origin server become corrupt, then Traffic Server will also use the generic partition to store content for that origin server (see <a href="files.htm#hosting.config">hosting.config</a>). </li>
+ <li>Save and close the <code>hosting.config</code> file. </li>
+ <li>Navigate to the Traffic Server <code>bin</code> directory. </li>
+ <li>Run the command <code>traffic_line -x</code> to apply the configuration changes. </li>
+</ol>
+<h2 id="ConfiguringCacheObjectSizeLimit">Configuring the Cache Object Size Limit</h2>
+<p>By default, Traffic Server allows objects of any size to be cached. You can change the default behavior and specify a size limit for objects in the cache via the steps below:</p>
+<ol>
+ <li>In a text editor, open the <code>records.config</code> file located in the Traffic Server <code>config</code> directory. </li>
+ <li>Edit the following variable:<br />
+ <table width="1232" border="1">
+ <tr>
+ <th width="322" scope="col">Variable</th>
+ <th width="894" scope="col">Description</th>
+ </tr>
+ <tr>
+ <td><code><i>proxy.config.cache.max_doc_size</i></code></td>
+ <td>Set this variable to specify the maximum size allowed for objects in the cache in bytes.<br /> Enter <code>0</code> (zero) if you do not want a size limit.</td>
+ </tr>
+ </table>
+ </li>
+ <li>Save and close the <code>records.config</code> file. </li>
+ <li>Navigate to the Traffic Server <code>bin</code> directory. </li>
+ <li>Run the command <code>traffic_line -x</code> to apply the configuration changes. </li>
+</ol>
+<h2 id="ClearingCache">Clearing the Cache</h2>
+
+<p>When you clear the cache, you remove all data from the entire cache - including data in the host database. You should clear the cache before performing certain cache configuration tasks, such as partitioning. You cannot clear the cache when Traffic Server is running. </p>
+<h5>To clear the cache: </h5>
+<ol>
+ <li>Stop Traffic Server (refer to <a href="getstart.htm#StoppingTrafficEdge">Stopping Traffic Server</a>). </li>
+ <li>Enter the following command to clear the cache:<br /><code>traffic_server -Cclear</code><br />The <code>clear</code> command deletes all data in the object store and the host database. Traffic Server does not prompt you to confirm the deletion. </li>
+ <li>Restart Traffic Server (refer to <a href="getstart.htm#StartingTrafficEdge">Starting Traffic Server</a>).</li>
+</ol>
+
+<h2 id="RemoveObjectFromCache">Removing an Object From the Cache</h2>
+<p>Traffic Server accepts the custom HTTP request method <code>PURGE</code> when removing a specific object from cache. If the object is found in the cache and is successfully removed, then Traffic Server responds with a <code>200 OK </code> HTTP message; otherwise, a <code>404 File Not Found</code> message is returned. </p>
+<p>In the following example, Traffic Server is running on the domain <u><code>example.com</code></u> and you want to remove the image <code>remove_me.jpg</code> from cache:</p>
+<p><code>$ curl -X PURGE -v "http://example.com/remove_me.jpg"</code></p>
+<p><code>* About to connect() to example.com port 80 (#0) <br />
+ * Trying 192.0.32.11... connected <br />
+ * Connected to example.com (192.0.32.11) port 80 (#0)</code></p>
+<p><code> > PURGE /remove_me.jpg HTTP/1.1 <br /> > User-Agent: curl/7.19.7 <br />
+ > Host: example.com <br /> > Accept: */* <br /> > <br /> < HTTP/1.1 200 Ok <br />
+ < Date: Thu, 08 Jan 2010 20:32:07 GMT <br /> < Connection: keep-alive</code></p>
+<p>The next time Traffic Server receives a request for the removed object, it will contact the origin server to retrieve it (i.e., it has been purged from the Traffic Server cache).</p>
+<p>Note: The procedure above only removes an object from a <i>specific</i> Traffic Server cache. Users may still see the old (removed) content if it was cached by intermediary caches or by the end-users' web browser.</p>
+<h2 id="InspectingCache">Inspecting the Cache</h2>
+<p>Traffic Server provides a Cache Inspector utility that enables you to view, delete, and invalidate URLs in the cache (HTTP only). The Cache Inspector utility is a powerful tool that's capable of deleting <i>all</i> the objects in your cache; therefore, make sure that only authorized administrators are allowed to access this utility. To control which hosts have access via the <code>mgmt_allow.config</code> file, see <a href="secure.htm#ControllingHostAccessTrafficManager">Controlling Host Access to Traffic Manager</a>. </p>
+<h3>Accessing the Cache Inspector Utility </h3>
+<p>To access the Cache Inspector utility, follow the steps below:</p>
+<ol>
+ <li>In a text editor, open the <code>records.config</code> file located in the Traffic Server <code>config</code> directory. </li>
+ <li>Add the following variable at the end of the file:<br /><code><i>CONFIG proxy.config.http_ui_enabled INT 1</i></code></li>
+ <li>To access the cache inspector in reverse proxy mode, you must add a remap rule to <code>remap.config</code> to expose the URL. <br />
+ For example: <br />
+ <code>map http://yourhost.com/myCI http://{cache} @action=allow @src_ip=corp_internal_address</code></li>
+ <li>From the Traffic Server <code>bin</code> directory, enter the following command to re-read the configuration file:<br />
+ <code>traffic_line -x</code></li>
+ <li>Open your web browser and configure it to use your Traffic Server as a proxy server. Type the following URL:
+<br /><code>http://{cache}</code></li>
+ <li>The Cache page opens (see <a href="#UsingCachePage">Using the Cache Page</a> below).</li>
+</ol>
+<h3 id="UsingCachePage">Using the Cache Page </h3>
+<p>The <b>Cache page</b> provides several options that enable you to view and delete the contents of your cache: </p>
+<ul>
+ <li>Click <strong>Lookup url</strong> to search for a particular URL in the cache. When Traffic Server finds the URL in the cache, it displays details about the object that corresponds to the URL (such as the header length and the number of alternates). From the display page, you can delete the URL from the cache. </li>
+ <li>Click <strong>Delete url</strong> to delete a particular URL or list of URLs from the cache. Traffic Server indicates if a delete is successful. </li>
+ <li>Click <strong>Regex lookup</strong> to search for URLs that match one or more regular expressions. From the display page, you can delete the URLs listed.<br />
+ For example, enter the following to search for all URLs that end in html and are prefixed with <code>http://www.dianes.com: <br />
+ http://www.dianes.com/.*\.html$</code></li>
+ <li>Click <strong>Regex delete</strong> to delete all URLs that match a specified regular expression.<br /> For example, enter the following to delete all HTTP URLs that end in <code>html</code>: <br /><code>http://.*\.html$</code> </li>
+ <li>Click <strong>Regex invalidate</strong> to invalidate URLs that match a specified regular expression. When you invalidate a URL, Traffic Server marks the object that corresponds to the URL as stale in the cache. Traffic Server then contacts the origin server to check if the object is still fresh (revalidates) before serving it from the cache. </li>
+</ul>
+<p><strong>Note:</strong> Only one administrator should delete and invalidate cache entries from the Cache page at any point in time. Changes made by multiple administrators at the same time can lead to unpredictable results.</p>
+
+
+<!--#include file="bottom.html" -->
\ No newline at end of file
Propchange: websites/staging/trafficserver/trunk/content/docs/v2/admin/cache.htm
------------------------------------------------------------------------------
svn:executable = *
Added: websites/staging/trafficserver/trunk/content/docs/v2/admin/cli.htm
==============================================================================
--- websites/staging/trafficserver/trunk/content/docs/v2/admin/cli.htm (added)
+++ websites/staging/trafficserver/trunk/content/docs/v2/admin/cli.htm Mon Dec 19 22:58:01 2011
@@ -0,0 +1,409 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">
+<html>
+<head>
+<title>Traffic Line Commands</title>
+
+<!--#include file="top.html" -->
+
+ <h1><a name="1053643">Appendix C - Traffic Line Commands</a>
+
+ </h1>
+ <p> This appendix contains the following sections: </p>
+
+<ul>
+<li><a href="#1053987">Traffic Line Commands</a></li>
+<li><a href="#1025718">Traffic Line Variables</a></li>
+</ul>
+<h2>
+ <a name="1053987">Traffic Line Commands</a> </h2>
+ <p> Use Traffic Line to execute individual Traffic Server commands and to script multiple commands in a shell. Execute Traffic Line commands from the Traffic Server <code>bin</code> directory. If the Traffic Server <code>bin</code> directory is not in your path, then prepend the Traffic Line command with <code>./</code> (for example: <code>./traffic_line -p</code>). </p>
+ <p> The following table describes all the commands available in Traffic Line. </p>
+ <table border="1">
+ <tr>
+ <th> <p> Command</p></th>
+ <th> <p> Description</p></th>
+ </tr>
+ <tr>
+ <td><p> <code> traffic_line -b</code> </p></td>
+ <td><p> Bounces Traffic Server on the local node. Bouncing Traffic Server shuts down and immediately restarts the Traffic Server node.</p></td>
+ </tr>
+ <tr>
+ <td><p> <code> traffic_line -c</code> </p></td>
+ <td><p> Clears accumulated statistics on the local node.</p></td>
+ </tr>
+ <tr>
+ <td><p> <code> traffic_line -h</code> </p></td>
+ <td><p> Displays a list of Traffic Line commands.</p></td>
+ </tr>
+ <tr>
+ <td><p> <code> traffic_line -p <em>socket_path</em></code> </p></td>
+ <td><p> Specifies location (directory and path) of the socket used for Traffic Line communication.<br />
+ The default path is: <code><em>install_dir</em> /config/cli</code> </p></td>
+ </tr>
+ <tr>
+ <td><p> <code> traffic_line -q</code> </p></td>
+ <td><p> Displays a list of the origin servers that are currently congested. </p>
+ <p> <b>Note:</b> To use this command, you must set the variable <code> <i>proxy.config.raf.enabled</i></code> to 1 and set the variable <code> <i>proxy.config.raf.port</i></code> to a different port <em CLASS="Emphasis"> only</em> if there is a conflict with the default port 9000.</p></td>
+ </tr>
+ <tr>
+ <td><p> <code> traffic_line -r <em>variable</em></code> </p></td>
+ <td><p> Displays specific performance statistics or a current configuration setting. For a list of the variables you can specify, see <a href="cli.htm#1025718">Traffic Line Variables</a>.</p></td>
+ </tr>
+ <tr>
+ <td><p> <code> traffic_line -s <em>variable</em> -v <em>value</em></code> </p></td>
+ <td><p> Sets configuration variables, where <code><i>variable</i></code> is the configuration variable you want to change and <code> <i>value</i></code> is the value you want to set. Refer to <a href="files.htm#records.config">records.config</a> for a list of the configuration variables you can specify.</p></td>
+ </tr>
+ <tr>
+ <td><p> <code> traffic_line -x</code> </p></td>
+ <td><p> Initiates a Traffic Server configuration file reread. Use this command after every configuration file modification.</p></td>
+ </tr>
+ <tr>
+ <td><p> <code> traffic_line -B</code> </p></td>
+ <td><p> Bounces all Traffic Server nodes in the cluster. Bouncing Traffic Server shuts down and immediately restarts Traffic Server, node-by-node.</p></td>
+ </tr>
+ <tr>
+ <td><p> <code> traffic_line -C</code> </p></td>
+ <td><p> Clears accumulated statistics on all nodes in the cluster.</p></td>
+ </tr>
+ <tr>
+ <td><p> <code> traffic_line -L</code> </p></td>
+ <td><p> Restarts the <code> traffic_manager</code> and <code> traffic_server</code> processes on the local node.</p></td>
+ </tr>
+ <tr>
+ <td><p> <code> traffic_line -M</code> </p></td>
+ <td><p> Restarts the <code> traffic_manager</code> process and the <code> traffic_server</code> process on all the nodes in a cluster.</p></td>
+ </tr>
+ <tr>
+ <td><p> <code> traffic_line -S</code> </p></td>
+ <td><p> Shuts down Traffic Server on the local node.</p></td>
+ </tr>
+ <tr>
+ <td><p> <code> traffic_line -U</code> </p></td>
+ <td><p> Starts Traffic Server on the local node.</p></td>
+ </tr>
+ </table>
+<p>
+ <strong><a name="1025718">Traffic Line Variables</a></strong>
+ </p>
+ <p> You can view statistics and change configuration options in Traffic Line by using specific variables. The variables used for gathering statistics are described below. The variables used for viewing and changing configuration options are described in <a href="files.htm#records.config">records.config</a>. For procedures about specifying the variables, refer to <a href="monitor.htm">Viewing Statistics from Traffic Line</a> and <a href="configure.htm">Configuring Traffic Server Using Traffic Line</a>. </p>
+<p> The variables used for viewing individual statistics are described in the following table. To view a statistic in Traffic Line, enter the command <code>traffic_line -r <em>variable</em> </code>at the prompt. </p>
+ <table border="1">
+ <tr>
+ <td><p><strong> Statistic</strong></p></td>
+ <td><p><strong> Variable</strong></p></td>
+ </tr>
+ <tr>
+ <td rowspan="1" colspan="2"><p><strong> Summary</strong></p></td>
+ </tr>
+ <tr>
+ <td><p> Node name</p></td>
+ <td><p> <i><code> proxy.node.hostname </code> </i></p></td>
+ </tr>
+ <tr>
+ <td><p> Objects served</p></td>
+ <td><p> <i><code> proxy.node.user_agents_total_documents_served</code> </i></p></td>
+ </tr>
+ <tr>
+ <td><p> Transactions per second</p></td>
+ <td><p> <i><code> proxy.node.user_agent_xacts_per_second</code> </i></p></td>
+ </tr>
+ <tr>
+ <td rowspan="1" colspan="2"><p><strong> Node</strong></p></td>
+ </tr>
+ <tr>
+ <td><p> Document hit rate </p></td>
+ <td><p> <i><code> proxy.node.cache_hit_ratio_avg_10s</code> </i></p>
+ <p> <i><code> proxy.cluster.cache_hit_ratio_avg_10s</code> </i></p></td>
+ </tr>
+ <tr>
+ <td><p> Bandwidth savings </p></td>
+ <td><p> <i><code> proxy.node.bandwidth_hit_ratio_avg_10s</code> </i></p>
+ <p> <i><code> proxy.cluster.bandwidth_hit_ratio_avg_10s </code> </i></p></td>
+ </tr>
+ <tr>
+ <td><p> Cache percent free</p></td>
+ <td><p> <i><code> proxy.node.cache.percent_free</code> </i></p>
+ <p> <i><code> proxy.cluster.cache.percent_free</code> </i></p></td>
+ </tr>
+ <tr>
+ <td><p> Open origin server connections</p></td>
+ <td><p> <i><code> proxy.node.current_server_connections</code> </i></p>
+ <p> <i><code> proxy.cluster.current_server_connections </code> </i></p></td>
+ </tr>
+ <tr>
+ <td><p> Open client connections </p></td>
+ <td><p> <i><code> proxy.node.current_client_connections</code> </i></p>
+ <p> <i><code> proxy.cluster.current_client_connections </code> </i></p></td>
+ </tr>
+ <tr>
+ <td><p> Cache transfers in progress </p></td>
+ <td><p> <i><code> proxy.node.current_cache_connections</code> </i></p>
+ <p> <i><code> proxy.cluster.current_cache_connections </code> </i></p></td>
+ </tr>
+ <tr>
+ <td><p> Client throughput (Mbits/sec)</p></td>
+ <td><p> <i><code> proxy.node.client_throughput_out</code> </i></p>
+ <p> <i><code> proxy.cluster.client_throughput_out</code> </i></p></td>
+ </tr>
+ <tr>
+ <td><p> Transactions per second </p></td>
+ <td><p> <i><code> proxy.node.user_agent_xacts_per_second </code> </i></p>
+ <p> <i><code> proxy.cluster.user_agent_xacts_per_second</code> </i></p></td>
+ </tr>
+ <tr>
+ <td><p> DNS lookups per second </p></td>
+ <td><p> <i><code> proxy.node.dns.lookups_per_second </code> </i></p>
+ <p> <i><code> proxy.cluster.dns.lookups_per_second </code> </i></p></td>
+ </tr>
+ <tr>
+ <td><p> Host database hit rate </p></td>
+ <td><p> <i><code> proxy.node.hostdb.hit_ratio_avg_10s</code> </i></p>
+ <p> <i><code> proxy.cluster.hostdb.hit_ratio_avg_10s </code> </i></p></td>
+ </tr>
+ <tr>
+ <td rowspan="1" colspan="2"><p><strong> HTTP</strong></p></td>
+ </tr>
+ <tr>
+ <td><p> Total document bytes from client</p></td>
+ <td><p> <i><code> proxy.process.http.user_agent_response_document_total_size</code> </i></p></td>
+ </tr>
+ <tr>
+ <td><p> Total header bytes from client</p></td>
+ <td><p> <i><code> proxy.process.http.user_agent_response_header_total_size</code> </i></p></td>
+ </tr>
+ <tr>
+ <td><p> Total connections to client</p></td>
+ <td><p> <i><code> proxy.process.http.total_client_connections</code> </i></p></td>
+ </tr>
+ <tr>
+ <td><p> Client transactions in progress</p></td>
+ <td><p> <i><code> proxy.process.http.current_client_transactions</code> </i></p></td>
+ </tr>
+ <tr>
+ <td><p> Total document bytes from origin server</p></td>
+ <td><p> <i><code> proxy.process.http.origin_server_response_document_total_size</code> </i></p></td>
+ </tr>
+ <tr>
+ <td><p> Total header bytes from origin server</p></td>
+ <td><p> <i><code> proxy.process.http.origin_server_response_header_total_size</code> </i></p></td>
+ </tr>
+ <tr>
+ <td><p> Total connections to origin server</p></td>
+ <td><p> <i><code> proxy.process.http.total_server_connections</code> </i></p></td>
+ </tr>
+ <tr>
+ <td><p> Origin server transactions in progress </p></td>
+ <td><p> <i><code> proxy.process.http.current_server_transactions</code> </i></p></td>
+ </tr>
+ <tr>
+ <td rowspan="1" colspan="2"><p><strong> ICP</strong></p></td>
+ </tr>
+ <tr>
+ <td><p> ICP query requests originating from this node</p></td>
+ <td><p> <i><code> proxy.process.icp.icp_query_requests</code> </i></p></td>
+ </tr>
+ <tr>
+ <td><p> ICP query messages sent from this node</p></td>
+ <td><p> <i><code> proxy.process.icp.total_udp_send_queries</code> </i></p></td>
+ </tr>
+ <tr>
+ <td><p> ICP peer hit messages received from this node</p></td>
+ <td><p> <i><code> proxy.process.icp.icp_query_hits</code> </i></p></td>
+ </tr>
+ <tr>
+ <td><p> ICP peer miss messages received from this node </p></td>
+ <td><p> <i><code> proxy.process.icp.icp_query_misses</code> </i></p></td>
+ </tr>
+ <tr>
+ <td><p> Total ICP responses received from this node</p></td>
+ <td><p> <i><code> proxy.process.icp.icp_remote_responses</code> </i></p></td>
+ </tr>
+ <tr>
+ <td><p> Average ICP message response time (ms) from this node</p></td>
+ <td><p> <i><code> proxy.process.icp.total_icp_response_time</code> </i></p></td>
+ </tr>
+ <tr>
+ <td><p> Average ICP request time (ms) from this node</p></td>
+ <td><p> <i><code> proxy.process.icp.total_icp_request_time</code> </i></p></td>
+ </tr>
+ <tr>
+ <td><p> Query messages received from ICP peers</p></td>
+ <td><p> <i><code> proxy.process.icp.icp_remote_query_requests</code> </i></p></td>
+ </tr>
+ <tr>
+ <td><p> Remote query hits from ICP peers</p></td>
+ <td><p> <i><code> proxy.process.icp.cache_lookup_success</code> </i></p></td>
+ </tr>
+ <tr>
+ <td><p> Remote query misses from ICP peers</p></td>
+ <td><p> <i><code> proxy.process.icp.cache_lookup_fail</code> </i></p></td>
+ </tr>
+ <tr>
+ <td><p> Successful response messages sent to peers</p></td>
+ <td><p> <i><code> proxy.process.icp.query_response_write</code> </i></p></td>
+ </tr>
+ <tr>
+ <td rowspan="1" colspan="2"><p><strong> Cache </strong></p></td>
+ </tr>
+ <tr>
+ <td><p> Bytes used</p></td>
+ <td><p> <i><code> proxy.process.cache.bytes_used</code> </i></p></td>
+ </tr>
+ <tr>
+ <td><p> Cache size</p></td>
+ <td><p> <i><code> proxy.process.cache.bytes_total</code> </i></p></td>
+ </tr>
+ <tr>
+ <td><p> Lookups in progress</p></td>
+ <td><p> <i><code> proxy.process.cache.lookup.active</code> </i></p></td>
+ </tr>
+ <tr>
+ <td><p> Lookups completed</p></td>
+ <td><p> <i><code> proxy.process.cache.lookup.success</code> </i></p></td>
+ </tr>
+ <tr>
+ <td><p> Lookup misses</p></td>
+ <td><p> <i><code> proxy.process.cache.lookup.failure</code> </i></p></td>
+ </tr>
+ <tr>
+ <td><p> Reads in progress</p></td>
+ <td><p> <i><code> proxy.process.cache.read.active</code> </i></p></td>
+ </tr>
+ <tr>
+ <td><p> Reads completed</p></td>
+ <td><p> <i><code> proxy.process.cache.read.success</code> </i></p></td>
+ </tr>
+ <tr>
+ <td><p> Read misses</p></td>
+ <td><p> <i><code> proxy.process.cache.read.failure</code> </i></p></td>
+ </tr>
+ <tr>
+ <td><p> Writes in progress</p></td>
+ <td><p> <i><code> proxy.process.cache.write.active</code> </i></p></td>
+ </tr>
+ <tr>
+ <td><p> Writes completed</p></td>
+ <td><p> <i><code> proxy.process.cache.write.success</code> </i></p></td>
+ </tr>
+ <tr>
+ <td><p> Write failures</p></td>
+ <td><p> <i><code> proxy.process.cache.write.failure</code> </i></p></td>
+ </tr>
+ <tr>
+ <td><p> Updates in progress</p></td>
+ <td><p> <i><code> proxy.process.cache.update.active</code> </i></p></td>
+ </tr>
+ <tr>
+ <td><p> Updates completed</p></td>
+ <td><p> <i><code> proxy.process.cache.update.success</code> </i></p></td>
+ </tr>
+ <tr>
+ <td><p> Update failures</p></td>
+ <td><p> <i><code> proxy.process.cache.update.failure</code> </i></p></td>
+ </tr>
+ <tr>
+ <td><p> Removes in progress</p></td>
+ <td><p> <i><code> proxy.process.cache.remove.active</code> </i></p></td>
+ </tr>
+ <tr>
+ <td><p> Remove successes</p></td>
+ <td><p> <i><code> proxy.process.cache.remove.success</code> </i></p></td>
+ </tr>
+ <tr>
+ <td><p> Remove failures</p></td>
+ <td><p> <i><code> proxy.process.cache.remove.failure</code> </i></p></td>
+ </tr>
+ <tr>
+ <td rowspan="1" colspan="2"><p> <strong> Host Database</strong> </p></td>
+ </tr>
+ <tr>
+ <td><p> Total lookups</p></td>
+ <td><p> <i><code> proxy.process.hostdb.total_lookups</code> </i></p></td>
+ </tr>
+ <tr>
+ <td><p> Total hits</p></td>
+ <td><p> <i><code> proxy.process.hostdb.total_hits</code> </i></p></td>
+ </tr>
+ <tr>
+ <td><p> Time TTL (min)</p></td>
+ <td><p> <i><code> proxy.process.hostdb.ttl</code> </i></p></td>
+ </tr>
+ <tr>
+ <td rowspan="1" colspan="2"><p> <strong> DNS</strong> </p></td>
+ </tr>
+ <tr>
+ <td><p> DNS total lookups</p></td>
+ <td><p> <i><code> proxy.process.dns.total_dns_lookups</code> </i></p></td>
+ </tr>
+ <tr>
+ <td><p> Average lookup time (msec)</p></td>
+ <td><p> <i><code> proxy.process.dns.lookup_avg_time</code> </i></p></td>
+ </tr>
+ <tr>
+ <td><p> DNS successes</p></td>
+ <td><p> <i><code> proxy.process.dns.lookup_successes</code> </i></p></td>
+ </tr>
+ <tr>
+ <td rowspan="1" colspan="2"><p><strong> Cluster </strong></p></td>
+ </tr>
+ <tr>
+ <td><p> Bytes read</p></td>
+ <td><p> <i><code> proxy.process.cluster.read_bytes</code> </i></p></td>
+ </tr>
+ <tr>
+ <td><p> Bytes written</p></td>
+ <td><p> <i><code> proxy.process.cluster.write_bytes</code> </i></p></td>
+ </tr>
+ <tr>
+ <td><p> Connections open</p></td>
+ <td><p> <i><code> proxy.process.cluster.connections_open</code> </i></p></td>
+ </tr>
+ <tr>
+ <td><p> Total operations</p></td>
+ <td><p> <i><code> proxy.process.cluster.connections_opened</code> </i></p></td>
+ </tr>
+ <tr>
+ <td><p> Network backups</p></td>
+ <td><p> <i><code> proxy.process.cluster.net_backup</code> </i></p></td>
+ </tr>
+ <tr>
+ <td><p> Clustering nodes</p></td>
+ <td><p> <i><code> proxy.process.cluster.nodes</code> </i></p></td>
+ </tr>
+ <tr>
+ <td rowspan="1" colspan="2"><p><strong> Logging </strong></p></td>
+ </tr>
+ <tr>
+ <td><p> Log files currently open</p></td>
+ <td><p> <i><code> proxy.process.log.log_files_open</code> </i></p></td>
+ </tr>
+ <tr>
+ <td><p> Space used for log files</p></td>
+ <td><p> <i><code> proxy.process.log.log_files_space_used</code> </i></p></td>
+ </tr>
+ <tr>
+ <td><p> Number of access events logged</p></td>
+ <td><p> <i><code> proxy.process.log.event_log_access</code> </i></p></td>
+ </tr>
+ <tr>
+ <td><p> Number of access events skipped</p></td>
+ <td><p> <i><code> proxy.process.log.event_log_access_skip</code> </i></p></td>
+ </tr>
+ <tr>
+ <td><p> Number of error events logged</p></td>
+ <td><p> <i><code> proxy.process.log.event_log_error</code> </i></p></td>
+ </tr>
+ <tr>
+ <td rowspan="1" colspan="2"><p><strong> Congestion Control</strong></p></td>
+ </tr>
+ <tr>
+ <td><p> Number of congestions Traffic Server has observed because the maximum number of connections was exceeded.</p></td>
+ <td><p> <i><code>proxy.process.congestion.congested_on_max_connection</code></i></p></td>
+ </tr>
+ <tr>
+ <td><p> Number of congestions Traffic Server has observed because of an OS response or timeout failure.</p></td>
+ <td><p><i><code>proxy.process.congestion.congested_on_conn_failures</code></i></p></td>
+ </tr>
+ </table>
+
+<!--#include file="bottom.html" -->
\ No newline at end of file
Propchange: websites/staging/trafficserver/trunk/content/docs/v2/admin/cli.htm
------------------------------------------------------------------------------
svn:executable = *