Skip to content
This repository was archived by the owner on Apr 10, 2025. It is now read-only.

Commit 0f2a6fc

Browse files
committed
Remove spurious warnings
backport change from 53add3a Remove about not having a downstream cache rebeaconing key configured. Fixes #1060
1 parent c925b48 commit 0f2a6fc

File tree

1 file changed

+5
-6
lines changed

1 file changed

+5
-6
lines changed

net/instaweb/rewriter/critical_finder_support_util.cc

Lines changed: 5 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -349,12 +349,11 @@ void PrepareForBeaconInsertionHelper(CriticalKeys* proto,
349349
return;
350350
}
351351

352-
if (driver->options()->IsDownstreamCacheIntegrationEnabled()) {
353-
// We can only get here if downstream cache integration was enabled, but
354-
// no downstream cache rebeaconing key was specified. So, put out a
355-
// warning message. Note that we do not put out this message on a per
356-
// request basis, because it will clutter up the logs. Instead we do it
357-
// only once every beaconing interval.
352+
if (driver->options()->IsDownstreamCacheIntegrationEnabled() &&
353+
!driver->options()->IsDownstreamCacheRebeaconingKeyConfigured()) {
354+
// Note that we do not put out this message on a per request basis, because
355+
// it will clutter up the logs. Instead we do it only once every beaconing
356+
// interval.
358357
driver->message_handler()->Message(
359358
kWarning,
360359
"You seem to have downstream caching configured on your server. "

0 commit comments

Comments
 (0)