InformAction Forums

I am attempting to create a system that my employer can use that will block traffic to non-whitelisted domains / IPs using user controlled whitelists and group whitelists. The system uses Squid to allow for browser compatibility. A custom error page redirects a browser's request to an Apache PHP MySQL server, which then allows the user to enter whitelist information (for themselves and for groups they have write permissions to).

I've run into a problem in building this system: whitelisting the domain in the URL is obviously not sufficient for modern day usage, as there are many other connections made to other domains. I haven't even begun to consider how to handle cross site scripting.

I am posting this here because I recognize that the NoScript developers will have a lot of experience with whitelisting domains, and what is involved. Do you have any suggestions on how to proceed? Should I consider starting a new "project"?

You may want to take a look at the ABE module in NoScript. It is ordinarily part of NoScript, but was designed to be capable of working as an independent request filter.

Unfortunately the problem of 'site X depends on sites A, B, and C, which in turn depend on D-Z', does not have a simple solution.