~squid/squid/3.4 : changes

~squid/squid/3.4 » Changes from revision 13244

From Revision 13244 to 13225

Rev	Summary	Authors	Tags	Date
13244	Do not override user defined -std option Do not override user defined -std option	Amos Jeffries		7 years ago
13243	Bug 4169: HIT marked as MISS when If-None-Match does not mat... Bug 4169: HIT marked as MISS when If-None-Match does not match	Garri Djavadyan		7 years ago
13242	Bug 3379: Combination of If-Match and a Cache Hit result in ... Bug 3379: Combination of If-Match and a Cache Hit result in TCP Connection Failure	Garri Djavadyan		7 years ago
13241	Bug 3290: authenticate_ttl not working for digest authentica... Bug 3290: authenticate_ttl not working for digest authentication	Garri Djavadyan		7 years ago
13240	Bug 4501: HTTP/1.1: normalize Host header Bug 4501: HTTP/1.1: normalize Host header	Amos Jeffries		7 years ago
13239	Bug 4515: regression after CVE-2016-4554 patch Bug 4515: regression after CVE-2016-4554 patch	Amos Jeffries		7 years ago
13238	Fix SIGSEGV in ESIContext response handling Fix SIGSEGV in ESIContext response handling HttpReply pointer was being unlocked without heving been locked. Resulting in a double-free. Make it use RefCount instead of manual locking to ensure locked/unlock is always symmetrical.	Amos Jeffries		7 years ago
13237	Bug 4455: SegFault from ESIInclude::Start Bug 4455: SegFault from ESIInclude::Start	Amos Jeffries		7 years ago
13236	Require exact match in Host header name lookup Require exact match in Host header name lookup	Amos Jeffries		7 years ago
13235	Fix several ESI element construction issues Fix several ESI element construction issues * Do not wrap active logic in assert(). * Fix localbuf array bounds checking. * Add Must() conditions to verify array writes will succeed	Amos Jeffries		8 years ago
13234	nullptr is a C++11 feature nullptr is a C++11 feature	Amos Jeffries		8 years ago
13233	cachemgr.cgi: use dynamic MemBuf for internal content genera... cachemgr.cgi: use dynamic MemBuf for internal content generation Using a fixed size buffer limits how big content lines can be. Modern HTTP is fast reaching the point where such limits are problematic. Also fixes incorrect uses of snprintf() by removing them.	Amos Jeffries		8 years ago
13232	pinger: Fix buffer overflow in Icmp6::Recv pinger: Fix buffer overflow in Icmp6::Recv	Yuriy M. Kaminskiy		8 years ago
13231	Bug 4323: Netfilter broken cross-includes with Linux 4.2 Bug 4323: Netfilter broken cross-includes with Linux 4.2	Francesco Chemolli		8 years ago
13230	Bug 4431: C code is not compiled with CFLAGS Bug 4431: C code is not compiled with CFLAGS	Marcos Mello		8 years ago
13229	Fix delay_parameters documentation Fix delay_parameters documentation	Amos Jeffries		8 years ago
13228	Bug 3696: crash when client delay pools are activated Bug 3696: crash when client delay pools are activated	Amos Jeffries		8 years ago
13227	3.4.14 3.4.14	Amos Jeffries	SQUID_3_4_14	8 years ago
13226	AUFS: Raise I/O queue congestion limits AUFS: Raise I/O queue congestion limits ... from 8 to 8196 before initial congestion message appears. Modern networks can be quite busy and even amateur installations have a much higher I/O throughput than Squid was originally designed for. This often results in a series of "Queue congestion" warnings appearing on startup before Squid learns what the local environment requires. The new limit helps to cater for this and reduce teh frequency of unnecessary warnings. They may still occur, so debug output is also updated to show what the queue length has grown to with each warning. Also updating the congestion counter from 32-bit to 64-bit unsigned since the new limit already consumes half the available growth bits in 32-bit integer. NP: this update was triggered by reports from admin with proxies needing to expand AIO queues to over 4K entries on startup.	Amos Jeffries		8 years ago
13225	Do not blindly forward cache peer CONNECT responses. Do not blindly forward cache peer CONNECT responses. Squid blindly forwards cache peer CONNECT responses to clients. This may break things if the peer responds with something like HTTP 403 (Forbidden) and keeps the connection with Squid open: - The client application issues a CONNECT request. - Squid forwards this request to a cache peer. - Cache peer correctly responds back with a "403 Forbidden". - Squid does not parse cache peer response and just forwards it as if it was a Squid response to the client. - The TCP connections are not closed. At this stage, Squid is unaware that the CONNECT request has failed. All subsequent requests on the user agent TCP connection are treated as tunnelled traffic. Squid is forwarding these requests to the peer on the TCP connection previously used for the 403-ed CONNECT request, without proper processing. The additional headers which should have been applied by Squid to these requests are not applied, and the requests are being forwarded to the cache peer even though the Squid configuration may state that these requests must go directly to the origin server. This fixes Squid to parse cache peer responses, and if an error response found, respond with "502 Bad Gateway" to the client and close the connections.	Alex Rousskov		8 years ago

Older »