trafficserver-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Alan Carroll <>
Subject Re: traffic server configuration
Date Fri, 27 Mar 2015 13:46:15 GMT
The best rule is to ask, what is the universe of origin servers you expect to access? If it
is finite and known, use reverse proxy. If it is potentially unlimited, use forward proxy.
But what real difference this makes, I don't know. Transparency is completely independent
of forward/reverse proxy and each side is independent of the other (you can have transparency
on just the user agent side, just the origin server side, or both). Getting transparent mode
to work can be a bit of a pain (since it requires configuration outside of ATS) so I would
avoid it unless you have a specific need for it. 

     On Friday, March 27, 2015 7:31 AM, Randeep <> wrote:

 Hi all,
We are configuring an ATS for caching on our network edge points. But I'm not getting how
to do it. This is our scenario. We have one central headend where we store the videos and
stream live channels and this headend is connected to our nationwide private network(MPLS
mesh). We are planning POP(caching) locations in every city. From these pop locations network
is connected to junction boxes and from there it is connected to customer devices. 

In this POP we are planning to put Apache traffic server as caching(videos-MPEG DASH Encrypted.)
server. I'm confused whether we have to configure this caching server as reverse proxy? Reverse
proxy can be configured transparent? 
Is there something wrong in it?Is this the right way to implement this? 
All suggestions are welcome.
Mob: +919447831699[kerala]
Mob: +919880050349[B'lore]

  • Unnamed multipart/mixed (inline, None, 0 bytes)
View raw message