bryancall opened a new pull request, #13731:
URL: https://github.com/apache/trafficserver/pull/13731

   We're retiring the old Confluence wiki 
(cwiki.apache.org/confluence/display/TS). Almost all of it is either history or 
already covered by these docs or the [GitHub 
wiki](https://github.com/apache/trafficserver/wiki). This PR moves the one page 
that had no replacement and repoints the links that still went to Confluence.
   
   - **New page: Traffic Shaping** 
(`doc/admin-guide/configuration/traffic-shaping.en.rst`). It covers marking 
packets with `SO_MARK` and DSCP and shaping them with Linux `tc`. It is written 
against today's `records.yaml`, the plugin API and the header_rewrite 
operators, rather than copying the 2014 page. It also spells out two things the 
old page missed:
     - Marking is off until the `PACKET_MARK` / `PACKET_TOS` bits are set in 
`sock_option_flag_in` / `sock_option_flag_out`.
     - `conf_remap` and `set-config` read values as decimal only, so `0x0c` 
becomes 0.
   - **The `records.yaml` entries and the four `TSHttpTxn*Packet*Set` API 
pages** now point to the new page instead of Confluence.
   - **Other Confluence links** in README.md, INSTALL, STATUS, README-EC2, 
AGENTS.md and `.claude/CLAUDE.md`, the installation guide, the developer guide 
and the `RamCacheCLFUS` comments now point to the docs site or the GitHub wiki.
   - **The developer guide's bug link** now goes to GitHub issues instead of 
the retired Jira project.
   
   `ci/jenkins/remap.config` still mentions cwiki, but nothing uses that file 
any more, so I left it alone. The Japanese `.po` files follow the English 
source.
   
   I built the docs with the pinned Sphinx using the dummy builder, and the 
only warnings are the extensions' existing parallel-read notices.
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to