rather than "transparent proxy"; switch the readme to match. also tweak the
wording to make it clear which firewall reals need to be on which machine
when having a router pass off http traffic to squid on a different machine
configured as an interception proxy.
New features include:
- SQL Database logging helper
- Time-Quota session helper
- Custom HTTP request headers
- SSL-Bump Server First
- Server Certificate Mimic
While there, add notes to README-main about increasing the number of
file descriptors via login.conf.
#ifdef'd headers to be used and dpb was junking it thus breaking the build;
fix by improving detection for backtrace_symbol_fd / libexecinfo and
explicitly using it.
no_ldap' block
- squid optionally uses atomic ops if available, however in the code
it requires 4 byte operations, whereas configure only tests for int.
change configure test which may give hppa a chance to build; breakage
reported by landry
This is merged from work by myself and Matthias Pitzl @ genua, thanks to
Rodolfo Gouveia for testing with NTLM.
Flavours have been removed:
- the external helper programs for NTLM/LDAP are now in subpackages:
squid-ldap and squid-ntlm.
- SNMP support is built by default in Squid 3.x so this has moved
to the main package (no external dependencies for this).
If the proxy server is running on the same subnet as the clients, the
return traffic from the proxy will go directly back to them without
ever hitting the firewall, which means the states will never get updated
and may fill-up your pflog(4) with blocked attempts. To circumvent this
the "no state" option needs to be specified for the route-to rule.
ok Brad, intput/ok sthen@ (maintainer)
is the maximum time rc.subr waits for a daemon, so usually it would end up
being forcefully killed (i.e. unclean shutdown -> cache must be rescanned
at next startup). suggested by aja@, diff from Brad.
- adjust PLIST to prevent warnings with pkg_delete -c, from aja@ ok Brad.
