By Dan Middlemiss, 2 December 2023 So, how bad can it get for the RCN and the CAF as a whole? During the past year, senior officers have been publicly […]
Word is reaching me that the number of designs under consideration for the AOR-JSS ship is down to only one. Apparently, the Spanish have been told that their Cantabria-class AOR […]
Canada’s decision to terminate the lease agreement for MV Wloclawek (IMO Registration No.: 8302313, pictured above) leaves the military without ready access to a sealift capability. You can read more […]
On Tuesday, 19 January, Murray Brewster of the Canadian Press filed a report that described the logistical problems confronting the Canadian Forces as they ramped up for Operation Hestia. Quoting […]
David Pugliese’s comment about the navy not wanting to move more ships to the west coast in response to a shifting strategic balance in that direction focuses, as most commentators […]
An article by Thom Shanker in New York Times on 12 January contains essential new information about how U.S. Marine Lieutenant General. Paul K. Van Riper, acting as the ‘enemy’ […]
Cookie Consent
At Canadian Naval Review (CNR), we are committed to respecting your privacy. When visiting our website for the first time you can either “Accept all” cookies (including ‘non-essential cookies’) or “Customize” your cookie preferences, which allows you to make individual choices and get details on the cookies we use.
Contains information related to marketing campaigns of the user. These are shared with Google AdWords / Google Ads when the Google Ads and Google Analytics accounts are linked together.
90 days
__utma
ID used to identify users and sessions
2 years after last activity
__utmt
Used to monitor number of Google Analytics server requests
10 minutes
__utmb
Used to distinguish new sessions and visits. This cookie is set when the GA.js javascript library is loaded and there is no existing __utmb cookie. The cookie is updated every time data is sent to the Google Analytics server.
30 minutes after last activity
__utmc
Used only with old Urchin versions of Google Analytics and not with GA.js. Was used to distinguish between new sessions and visits at the end of a session.
End of session (browser)
__utmz
Contains information about the traffic source or campaign that directed user to the website. The cookie is set when the GA.js javascript is loaded and updated when data is sent to the Google Anaytics server
6 months after last activity
__utmv
Contains custom information set by the web developer via the _setCustomVar method in Google Analytics. This cookie is updated every time new data is sent to the Google Analytics server.
2 years after last activity
__utmx
Used to determine whether a user is included in an A / B or Multivariate test.
18 months
_ga
ID used to identify users
2 years
_gali
Used by Google Analytics to determine which links on a page are being clicked
30 seconds
_ga_
ID used to identify users
2 years
_gid
ID used to identify users for 24 hours after last activity
24 hours
_gat
Used to monitor number of Google Analytics server requests when using Google Tag Manager