Find file History
Pull request Compare This branch is 28 commits behind pkrumins:master.
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Failed to load latest commit information.


this dir contains config files for nodejs-proxy.
they include:

* allow_ip_list - a file that contains allowed ips
* black_list    - a file that contains blocked urls (can be regexes)
* hostfilters.js- a file that contains JSON host special actions

hostfilters is used to define special actions to take. All rules are of the form
"target host:port" => action(s)
Currently, the proxy code tries to find a rule with the following priority :
1) domain:port
2) domain
3) *:port => default rule for incomming connections to port 80
4) *      => default rule
5) default: proxyto what the host directive contains ;-)

Please note that the rules are based on the *target* host:port located in the 
"host" header of the http request. For example, the real target port **may** be
different from the listening port on this server.

We currently support only 2 kind of rules, they are looked up with the following 
priority :
1) redirect => will issue a 301 to the browser
2) proxyto  => will lead to a "regular" reverse proxying
3) default is to proxy
Note that user authentication is *always* performed **before**. See bellow for 
more informations on athentication

It is also possible to specify authorization criterion. This is done using the
"Basic" http authentication scheme as defined in RFC 2617. "Digest" is not (yet ?)
supported. Since this reverse proxy is not seen by the useragent as a real proxy,
we can not use proxy-authenticate. This is sad because it prevents you from dong
http authentication on the other side as soon as you do not use the same credentials.
Passwords SHALL be written un-encrypted at the moment.
If you are planing on doing authentication on the application side, please do not
use this feature as it will break it !

NOTA: only http is supported, no HTTPS yet

        "hostname.domain.tld": {
            "redirect": ""
            "proxyto": "localhost:80",
            "description":"Very secret project here ;-)"

A security preventing proxying loop is harcoded. A request that has been proxied 
once will not be able to go thru a second time. Please let me know if this is a 
limitation for you (jtlebi on github).