Jon Rosamond, writing for IHS Jane’s Navy International, has an article entitled “Canada turns to Asterix for stop gap at-sea support.” The article was published on 04 October 2015. Rosamond […]
It is reasonable that the Department of National Defence1 (DND) is considering (conducting a “staff check,” to use military language as also used by an interviewee in a television report […]
Defence Industry Daily (13 Oct 10 – “Canada’s C$2.9 B “Joint Support Ship” Project, Take 2”) and Dave Pugliese’s Defence Watch (20 Oct 10 – “Joint Support Ship Less Capable But Air […]
The announcement on the evening of Friday, August 22, 2008 of the cancellation of the JSS procurement should have been no surprise to any observer of naval and military affairs. […]
The unexpected press release announcing the termination of procurement processes for two new types of ships for the Canadian Coast Guard and navy was no doubt a heavy blow. And […]
The Canadian navy’s sea-lift capacity has been mentioned previously in these quarters, in the context of the rumoured Conservative plan to pay-off the existing Protecteur-class replenishment ships a full two […]
Amidst the hoopla surrounding the leaked Conservative Canada First Defence Strategy and the subsequent series of articles by David Pugliese, one overlooked item was the proposed creation of a 250 […]
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
