Bug 1508288 - nsHostResolver::mOriginSuffix is not used, we should remove it. r=valentin
authorDragana Damjanovic <dd.mozilla@gmail.com>
Tue, 20 Nov 2018 21:58:17 +0000
changeset 503901 c9dfaa111bccdd127209ef5d1bf366de314f5e80
parent 503900 395b95afd795a02a49d609cdbb3857274a02276f
child 503902 85c1c4e2b17e12286b897a59c9e2f1727b2bac3c
push id10290
push userffxbld-merge
push dateMon, 03 Dec 2018 16:23:23 +0000
treeherdermozilla-beta@700bed2445e6 [default view] [failures only]
perfherder[talos] [build metrics] [platform microbench] (compared to previous push)
reviewersvalentin
bugs1508288
milestone65.0a1
first release with
nightly linux32
nightly linux64
nightly mac
nightly win32
nightly win64
last release without
nightly linux32
nightly linux64
nightly mac
nightly win32
nightly win64
Bug 1508288 - nsHostResolver::mOriginSuffix is not used, we should remove it. r=valentin Differential Revision: https://phabricator.services.mozilla.com/D12301
netwerk/dns/nsHostResolver.h
--- a/netwerk/dns/nsHostResolver.h
+++ b/netwerk/dns/nsHostResolver.h
@@ -130,18 +130,16 @@ protected:
     // When the record is no longer valid (it's time of expiration)
     mozilla::TimeStamp mValidEnd;
 
     // When the record enters its grace period. This must be before mValidEnd.
     // If a record is in its grace period (and not expired), it will be used
     // but a request to refresh it will be made.
     mozilla::TimeStamp mGraceStart;
 
-    const nsCString mOriginSuffix;
-
     mozilla::net::ResolverMode mResolverMode;
 
     uint16_t  mResolving;  // counter of outstanding resolving calls
 
     uint8_t negative : 1;   /* True if this record is a cache of a failed lookup.
                                Negative cache entries are valid just like any other
                                (though never for more than 60 seconds), but a use
                                of that negative entry forces an asynchronous refresh. */