Date: Thu, 28 Aug 2014 13:09:51 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-ports-bugs@FreeBSD.org Subject: [Bug 192980] www/squid33 - Wrong option using make config for STRICT_HTTP Message-ID: <bug-192980-13-0TM8zXUY2d@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-192980-13@https.bugs.freebsd.org/bugzilla/> References: <bug-192980-13@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=192980 Lawrence Chen <beastie@tardisi.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |beastie@tardisi.com --- Comment #17 from Lawrence Chen <beastie@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.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-192980-13-0TM8zXUY2d>