From a1755468fbb113a02d675311e84322f91cddb5b8 Mon Sep 17 00:00:00 2001 From: Aaron Schulz Date: Tue, 23 Apr 2019 11:37:53 -0700 Subject: [PATCH] Hypenate ChronologyProtector HTTP headers Follow up to 6b6997dcf9036e372b4 Change-Id: I4c26c16821f3b57996c7d5c7195010c57a603041 --- includes/Setup.php | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/includes/Setup.php b/includes/Setup.php index bf363ab50e..071b7c6feb 100644 --- a/includes/Setup.php +++ b/includes/Setup.php @@ -736,10 +736,10 @@ $cpPosInfo = LBFactory::getCPInfoFromCookieValue( MediaWikiServices::getInstance()->getDBLoadBalancerFactory()->setRequestInfo( [ 'IPAddress' => $wgRequest->getIP(), 'UserAgent' => $wgRequest->getHeader( 'User-Agent' ), - 'ChronologyProtection' => $wgRequest->getHeader( 'MediaWiki-ChronologyProtection' ), + 'ChronologyProtection' => $wgRequest->getHeader( 'MediaWiki-Chronology-Protection' ), 'ChronologyPositionIndex' => $wgRequest->getInt( 'cpPosIndex', $cpPosInfo['index'] ), 'ChronologyClientId' => $cpPosInfo['clientId'] - ?? $wgRequest->getHeader( 'MediaWiki-ChronologyClientId' ) + ?? $wgRequest->getHeader( 'MediaWiki-Chronology-Client-Id' ) ] ); unset( $cpPosInfo ); // Make sure that object caching does not undermine the ChronologyProtector improvements -- 2.20.1