Stats view IP whitelist about chihaya HOT 6 CLOSED

We actually recommend putting something like nginx in front of Chihaya. nginx can handle SSL for you and keep routes private that you don't want exposed.

from chihaya.

This would be a nice-to-have though, either via IP whitelist or API key or something.

from chihaya.

Yes nginx in-front of the Chihaya would work for the stats will work wonders. but would it not be better to have the announce/scrapes not go through nginx since another another link in the chain?

and since the stats and the tracker lives on the same URI then we will have to both or non over nginx proxy.

I am not sure about that part though

from chihaya.

and since the stats and the tracker lives on the same URI then we will have to both or non over nginx proxy.

The location directive in nginx will let you specify routes that you want public and ones that you don't.

I wouldn't worry about the extra hop from nginx->chihaya.

from chihaya.

Though in this case the feature is so small, simple, and obvious that I think it's worth including.

from chihaya.

I think IP whitelists/blacklists should implemented at the IP layer and not the application layer. Going to draw a line in the sand and say you should use iptables or the like rather then having us add more code that requires persistent storage into chihaya.

from chihaya.