Page History

...

Unlike the configuration variables the API functions work whether the socket has already been created or not. They immediately update an existing socket and the options are also get applied when a new socket is eventually created.

...

I wonder how the current implementation works with persistent connections? For example I suspect if you set a socket option per transaction and then reuse the connection to make for another origin request or if the client reuses it to make another request, the option doesn't get reset?

...

Traffic Server and iproute2 can be on different devices. It communicates the priority to iproute2 in the ToS/DiffServ Field which it overrides with the tos_out configuration variable and the conf_remap plugin. It shapes traffic sent *from* the origin by copying the priority from the ToS/DiffServ Field to the connection mark. The origin connection is transparent so iproute2 can tell which client the traffic belongs to. The client connection is transparent so Traffic Server can get the address of the origin in the rare case that a client neglects to send a Host header (HTTP/1.0 doesn't require it). You could alternatively configure the each client to use the proxy explicitly.

...