Repair 304 body retention and connection metadata

Review the independently proposed patch below, including its unchanged callers. A 304 carries replacement metadata, not a replacement entity body. Keep the cached payload and remove every Connection-nominated field as well as fixed hop-by-hop headers.

Review focus: HTTP caching

src/services/revalidation.go

BeforeProposed

+1−1

3434 headers[name] = value

3535 }

3636 }

37 return map[string]any{"status": request.Stored.Status, "body": request.Response.Body, "headers": headers}, nil

37 return map[string]any{"status": request.Stored.Status, "body": request.Stored.Body, "headers": headers}, nil

3838}

Your review

0 / 10,000 characters · A verdict needs supporting evidence.

30 more characters to give a verdict