Absolutely. Disable most of filters except for the most imortant ones like Content Filter and Blacklist. Configure content categories you want to block. Use traffic reports. Don't try to do too much filtering in a multi-user environment (some fragile websites will inevitably be broken).
A cusomer wrote:
"The only drawback is I have to manually configure each client's browsers to add the proxy. This leaves the door open for the users to re-configure their own browsers to go directly to the router and avoid the proxy. "
This is doable, but it's outside the scope of this application. Foxy is an HTTP proxy server, no more, no less.
One way to achieve this would be to configure your router/gateway to reject outgoing TCP traffic with destination ports 80 (HTTP), 8080 (and a few other ports common for public HTTP proxies). This way the users will have to configure their browsers to go through the box running Foxy (for which those ports should be open).
Another way is to run Foxy as a transparent proxy. Configure your gateway to rewrite TCP/IP packets with external destination IP addresses and port numbers 80, 8080, etc. replacing those two parameters with IP address of the box where Foxy is running and Foxy port number. This way the users' browsers won't even know they are using a proxy and won't need any configuration. No special Foxy configuration is neccessary either.
In a small network these things can be easily achieved with an old box with 2 network cards and no monitor running Linux or FreeBSD. For more information google for “trasparent HTTP proxy”.
Note: The pseudo domain feature and Shortcut Filter will not work in transparent proxy mode.
Even the most neutral filters break some fragile web site designs (e.g. replacing the outgoing User-Agent HTTP header with a random value makes Canadian Tire website enter an endless loop).
If you are lazy, simply add your broken domains to whitelist. Otherwise, you could try to find out which filter is to blame (see log, crunch_log, http_log, -v command line option), and add your site to the exception list of that filter (see exclude).
This is expected behavior. In general, content is pumped through a chain of filters, any of which can potentially modify it on the fly. So Foxy cannot send Content-Length header to the client when download begins, since the length may change. Instead, transfer is always chunked on the client side ("Transfer-Encoded: Chunked" HTTP header), so you browser cannot estimate download time, show progress bar, etc. [In version 1.6.4+ browsers should show progress indicator for most lengthy downloads.]
No. Go away.