Skip to content
This repository has been archived by the owner on Apr 21, 2023. It is now read-only.

Commit

Permalink
Remove spurious warnings
Browse files Browse the repository at this point in the history
backport change from 53add3a
Remove about not having a downstream cache rebeaconing key configured.
Fixes #1060
  • Loading branch information
crowell committed May 11, 2015
1 parent c925b48 commit 0f2a6fc
Showing 1 changed file with 5 additions and 6 deletions.
11 changes: 5 additions & 6 deletions net/instaweb/rewriter/critical_finder_support_util.cc
Original file line number Diff line number Diff line change
Expand Up @@ -349,12 +349,11 @@ void PrepareForBeaconInsertionHelper(CriticalKeys* proto,
return;
}

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

0 comments on commit 0f2a6fc

Please sign in to comment.