[Bug 192980] www/squid33 - Wrong option using make config for STRICT_HTTP
bugzilla-noreply at freebsd.org
bugzilla-noreply at freebsd.org
Thu Aug 28 13:09:52 UTC 2014
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=192980
Lawrence Chen <beastie at tardisi.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |beastie at tardisi.com
--- Comment #17 from Lawrence Chen <beastie at tardisi.com> ---
There should be a note that this option that used to be enabled by default is
now disabled by default, so that people wondering why their configuration that
worked with 3.3.11_4 stopped working with PORTREVISIONS after this.
Up to 3.3.11_4
enabling STRICT_HTTP ==> --disable-http-violations. So OPTIONS_DEFAULT of not
setting this, mean http-violations were enabled.
In _5 it was changed to *CONFIGURE_ENABLE=, inverting the behavior and
inverting the previously inverted logic. So, not setting STRICT_HTTP suddenly
meant 'strict_http' was set (as it would disable http violations.)
Changing the name to LAX_HTTP clarified the relationship of the options knob to
the configure option, but did not restore the previous default behavior that it
was enabled. Or make clear that this was needed to restore things to previous
defaults.
I have refresh_patterns that violate HTTP to try to make our squid proxies keep
files relating to updates for Microsoft, Linux and FreeBSD in cache longer....
--
You are receiving this mail because:
You are the assignee for the bug.
More information about the freebsd-ports-bugs
mailing list