~gary-wzl77/squid/ipc_prefix : changes

~gary-wzl77/squid/ipc_prefix » Changes from revision 14150

From Revision 14131 to 14112

Rev	Summary	Authors	Tags	Date
14131	SourceFormat Enforcement SourceFormat Enforcement	Source Maintenance		7 years ago
14130	SourceFormat Enforcement SourceFormat Enforcement	Source Maintenance		7 years ago
14129	Bug 3940 pt2: Make 'cache deny' do what is documented Bug 3940 pt2: Make 'cache deny' do what is documented Instead of overriding whatever cacheability was previously set to (including changing non-cacheables to be cacheable) actually prevent both cache read and write.	Amos Jeffries		7 years ago
14128	3.5.23 3.5.23	Amos Jeffries	SQUID_3_5_23	7 years ago
14127	Do not share private responses with collapsed client(s). Do not share private responses with collapsed client(s). This excessive sharing problem with collapsed forwarding code has several layers. In most cases, the core CF code does not share uncachable or private response with collapsed clients because of the refreshCheckHTTP() check. However, some responses might not be subject to that (or equivalent) check. More importantly, collapsed revalidation code does not check its responses at all and, hence, easily shares private responses. This short-term fix incorrectly assumes that an entry may become private (KEY_PRIVATE) only when it cannot be shared among multiple clients (e.g., because of a Cache-Control:private response header). However, there are a few other cases when an entry becomes private. One of them is a DISK_NO_SPACE_LEFT error inside storeSwapOutFileClosed() where StoreEntry::releaseRequest() sets KEY_PRIVATE for a sharable entry [that may still be perfectly preserved in the memory cache]. Consequently, the short-term fix reduces CF effectiveness. The extent of this reduction is probably environment-dependent. Also: do not re-use SET_COOKIE headers for collapsed revalidation slaves, i.e., adhere to the same requirement as for regular response HITs.	Eduard Bagdasaryan		7 years ago
14126	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
14125	Bug 3940 (partial): hostHeaderVerify failures MISS when they... Bug 3940 (partial): hostHeaderVerify failures MISS when they should be HIT This fixes the critical condition leading to the HIT. However not all code is correctly setting flags.noCache and flags.cacheable (see bugzilla). So there may be other fixes needed after this.	Garri Djavadyan		7 years ago
14124	HTTP/1.1: Add registered codes entry for new 103 (Early Hint... HTTP/1.1: Add registered codes entry for new 103 (Early Hints) status code	Amos Jeffries		7 years ago
14123	Bug 2258: bypassing cache but not destroying cache entry Bug 2258: bypassing cache but not destroying cache entry	Garri Djavadyan		7 years ago
14122	SourceFormat Enforcement SourceFormat Enforcement	Source Maintenance		7 years ago
14121	Bug 4406: SIGSEV in TunnelStateData::handleConnectResponse()... Bug 4406: SIGSEV in TunnelStateData::handleConnectResponse() during reconfigure and restart	Michael Buchau		7 years ago
14120	Support IPv6 NAT with PF for NetBSD and FreeBSD Support IPv6 NAT with PF for NetBSD and FreeBSD	Egervary Gergely		7 years ago
14119	Bug 4174 partial: fix Write.cc:41 "!ccb->active()" assertion... Bug 4174 partial: fix Write.cc:41 "!ccb->active()" assertion. The following sequence of events triggers this assertion: - The server sends an 1xx control message. - http.cc schedules ConnStateData::sendControlMsg call. - Before sendControlMsg is fired, http.cc detects an error (e.g., I/O error or timeout) and starts writing the reply to the user. - The ConnStateData::sendControlMsg is fired, starts writing 1xx, and hits the "no concurrent writes" assertion. We could only reproduce this sequence in the lab after changing Squid code to trigger a timeout at the right moment, but the sequence looks plausible. Other event sequences might result in the same outcome. To avoid concurrent writes, Squid now drops the control message if Http::One::Server detects that a reply is already being written. Also, ConnStateData delays reply writing until a pending control message write has been completed. This is a Measurement Factory project.	Christos Tsantilas		7 years ago
14118	Bug 3290: authenticate_ttl not working for digest authentica... Bug 3290: authenticate_ttl not working for digest authentication	Garri Djavadyan		7 years ago
14117	Bug 4007: Hang on DNS query with dead-end CNAME Bug 4007: Hang on DNS query with dead-end CNAME DNS lookup recursion no longer occurs. ipcacheParse() return values are no longer useful. Also, cleanup the debugging output.	Stephen Baynes		7 years ago
14116	Bug 3533: Cache still valid after HTTP/1.1 303 See Other Bug 3533: Cache still valid after HTTP/1.1 303 See Other RFC7231 does not mention 303 response as non-cacheable. So, assuming that means it is cacheable.	Garri Djavadyan		7 years ago
14115	Bug 4004 partial: Fix segfault via Ftp::Client::readControlR... Bug 4004 partial: Fix segfault via Ftp::Client::readControlReply Added nil dereference checks for Ftp::Client::ctrl.conn, including: - Ftp::Client::handlePasvReply() and handleEpsvReply() that dereference ctrl.conn in DBG_IMPORTANT messages. - Many functions inside FtpClient.cc and FtpGateway.cc files. TODO: We need to find a better way to handle nil ctrl.conn. It is only a matter of time when we forget to add another dereference check or discover a place we missed during this change. Also disabled forwarding of EPRT and PORT commands to origin servers. Squid support for those commands is broken and their forwarding may cause segfaults (bug #4004). Active FTP is still supported, of course. This is a Measurement Factory project	Christos Tsantilas		7 years ago
14114	Improve debugs warnings when loading signing certs fails Improve debugs warnings when loading signing certs fails	Amos Jeffries		7 years ago
14113	TLS: Make key= before cert= an error instead of quietly hidi... TLS: Make key= before cert= an error instead of quietly hiding the issue This squid.conf setup is fatal in Squid-4. So best to fix these installations. Even though Squdi-3 can cope with it.	Amos Jeffries		7 years ago
14112	Honor SBufReservationRequirements::minSize regardless of ide... Honor SBufReservationRequirements::minSize regardless of idealSize. In a fully specified SBufReservationRequirements, idealSize would naturally match or exceed minSize. However, the idealSize default value (zero) may not. We should honor minSize regardless of idealSize, just as the API documentation promises to do. No runtime changes expected right now because the only existing user of SBufReservationRequirements sets .idealSize to CLIENT_REQ_BUF_SZ (4096) and .minSize to 1024.	Alex Rousskov		7 years ago

Older »