TRAFFIC_WCCP(1)

📦
version 9.2.5 · 4 versions
, in ubuntu noble, ubuntu questing

💖 TRAFFIC_WCCP — ok bestie, let's talk 💖

so this is traffic_wccp(1), the Traffic Server WCCP client, from the Apache Traffic Server fam. sit down, grab a strawberry 🍓, we're doing this.

✨ NAME ✨

traffic_wccp — your Traffic Server WCCP client, periodt. 👑

🌸 SYNOPSIS 🌸

traffic_wccp [--address IP] [--router IP] [--service PATH] [--debug] [--daemon]

ngl it's giving "tiny program, big responsibilities".

🦋 DESCRIPTION 🦋

okay so traffic_wccp is literally a front end to the wccp client library. it's a stand-alone program (main character energy, no dependencies on your other drama 💅) and it speaks the client side of the WCCP cache protocol.

here's the tea: you can run this instead of the built-in WCCP feature in Traffic Server. and when is that a vibe? when you've got multiple programs running on the same computer that are all relying on WCCP to redirect traffic from the router over to the computer. so instead of everybody fighting over the built-in thing, this lil guy handles it. obsessed. 🫶

⚠️ but listen — because it relies on the wccp library, traffic_wccp is only built if Traffic Server is configured with --enable-wccp. no flag, no program. that's just the rules, bestie.

and if you want the overall Apache Traffic Server WCCP configuration documentation, it's at WCCP Configuration. go read it, it's iconic. ✨

💅 OPTIONS 💅

  • --address — IP address to bind. that's the address, you're binding it. 💖
  • --router — Bootstrap IP address for routers. this is where your routers get their start-from info. 🎀
  • --service — Path to service group definitions. yes queen, point it at the file.
  • --debug — Print debugging information. for when you need to see everything that's happening. 🙈
  • --daemon — Run as daemon. go live in the background, you deserve it. 🧚

🫶 the important part 🫶

you need to run at least with the --service arguments. like, that one is not optional. it's the whole point.

there's an example service definition file — service-nogre-example.config — included in the src/traffic_wccp directory. use it as your blueprint. 🌈

in this file you:

  • define your MD5 security password — highly recommended, like genuinely please do this 💀
  • define your service groups

the details of the service file are defined at WCCP Service Configuration. iykyk.

😭 LIMITATIONS 😭

ok so, the current WCCP implementation associated with ATS only supports one cache client per service group per router. one. that's it. that's the limit.

and the cache assignment logic? it currently assigns the current cache client to all buckets. all of them. no cap. so don't come at it expecting fancy load balancing, bestie, it's not that girl (yet).

2026, dev@trafficserver.apache.org

and that's the whole page, bestie!! this was version 9.2, dated Feb 12, 2026 — go forth and speak WCCP, you absolute icon 💜🦋✨

📦 where this page comes from