Hi, Leif Hedstrom. Thank you for your response. Let me explain what I am trying to achieve.
1. https://npmjs.org is a site where *public* node packages (think some tarballs) are published. For ex., http://registry.npmjs.org/request/-/request-0.10.0.tgz 2. I have setup a similar registry to host my private node packages, assume, it is running in http://private.npm-repo:8080/ 3. Instead of replicating all the public packages to my private registry, I am thinking for the following setup. 4. I will inform everybody in my team to access, say http://myregistry:8000/, for all the node pakages. 5. I will start ATS on http://myregistry:8000/ which will act as a caching proxy for both http://private.npm-repo:8080/ and https://npmjs.org -- Prabhakhar K On Tue, Aug 7, 2012 at 1:15 PM, Leif Hedstrom <zw...@apache.org> wrote: > On 8/7/12 2:01 PM, P Kaliyamurthy wrote: > >> Thank you for the reply. >> >> If you mean >> http://trafficserver.apache.**org/docs/trunk/admin/forward-** >> proxy/index.en.html<http://trafficserver.apache.org/docs/trunk/admin/forward-proxy/index.en.html> >> , >> I exactly followed that. >> >> The issue is ATS is not following the redirects, instead sends back 302. >> > > I'm not sure exactly what you are trying to do. I get the impression you > are setting up a reverse proxy (and not a forward proxy?). If the origin > sends back a 301 to ATS, then ATS will simply send that back to the client > (as it should). > > I think we have to take a step back, and understand exactly what you are > trying to achieve. > > -- Leif > >
