Cookies are small data files that websites place on your computer, laptop or mobile device.

Our use of CookiesWe use Cookies for the following purposes:

- To improve the performance of our websites by understanding which parts work well, and which don't.

- To enable us to collect information about how you and other people use our websites.

What Cookies do we use?We use the following Cookies

Session (Strictly necessary) CookiesThese are Cookies that are required for the operation of our website. They are necessary for the safety, security and integrity of the site. For example they help support the structure of the pages that are displayed to you, help to improve navigation and allow you to return to pages you have previously visited. This type of Cookie only lasts for the duration of the time you are visiting the website. When you leave the website they are deleted automatically.

Performance Cookies or analytical CookiesThese allow us to recognise and count the number of visitors and to see how visitors move around our website when they are using it. This helps us to improve the way our website works, for example, by ensuring that users are finding what they are looking for easily. The data is aggregated and anonymised, which means we cannot identify you as an individual.

Cookies used on this site and their Privacy Attributes

591c8f279d9d36bc6139c28f6e9a892bType: HTTP CookieDomain: www.cobweb.ieThe cookie is only valid during current browser session and it will be deleted when you close browserhttpOnly This cookie is not readable by client-side JavaScript code

apbct_timestampType: HTTP CookieDomain: www.cobweb.ieThe cookie is only valid during current browser session and it will be deleted when you close browserhttpOnly This cookie can be read by client-side JavaScript which might increase chances of stealing it in case of a successful Cross-Side Scripting attack. It's recommended that cookies storing authentication-related session token are protected by the flag

apbct_cookies_testType: HTTP CookieDomain: www.cobweb.ieThe cookie is only valid during current browser session and it will be deleted when you close browserhttpOnly This cookie can be read by client-side JavaScript which might increase chances of stealing it in case of a successful Cross-Side Scripting attack. It's recommended that cookies storing authentication-related session token are protected by the flag

ct_cookies_testType: HTTP CookieDomain: www.cobweb.ieThe cookie is only valid during current browser session and it will be deleted when you close browserhttpOnly This cookie can be read by client-side JavaScript which might increase chances of stealing it in case of a successful Cross-Side Scripting attack. It's recommended that cookies storing authentication-related session token are protected by the flagSize: 32 bytesSample value:60cc3cf31c3c68b8747120682dff1537

ct_ps_timestampType: HTTP CookieDomain: www.cobweb.ieThe cookie is only valid during current browser session and it will be deleted when you close browserhttpOnly This cookie can be read by client-side JavaScript which might increase chances of stealing it in case of a successful Cross-Side Scripting attack. It's recommended that cookies storing authentication-related session token are protected by the flagSize: 10 bytesSample value:1529415872This cookie seems to be a hexadecimal-encoded data. Attempted decoded value:b'\x15)AXr'Shannon entropy: 2.32Bit length: 40Cookie classification: same-origin session

ct_fkp_timestampType: HTTP CookieDomain: www.cobweb.ieThe cookie is only valid during current browser session and it will be deleted when you close browserhttpOnly This cookie can be read by client-side JavaScript which might increase chances of stealing it in case of a successful Cross-Side Scripting attack. It's recommended that cookies storing authentication-related session token are protected by the flagSize: 1 bytesSample value:0This cookie seems to be a hexadecimal-encoded data. Attempted decoded value:b'\x00'Shannon entropy: 0.00Bit length: 8Cookie classification: same-origin session

ct_pointer_dataType: HTTP CookieDomain: www.cobweb.ieThe cookie is only valid during current browser session and it will be deleted when you close browserhttpOnly This cookie can be read by client-side JavaScript which might increase chances of stealing it in case of a successful Cross-Side Scripting attack. It's recommended that cookies storing authentication-related session token are protected by the flagSize: 1 bytesSample value:0This cookie seems to be a hexadecimal-encoded data. Attempted decoded value:b'\x00'Shannon entropy: 0.00Bit length: 8Cookie classification: same-origin session

_gidType: HTTP CookieDomain: cobweb.ieThe cookie is only valid during current browser session and it will be deleted when you close browserhttpOnly This cookie can be read by client-side JavaScript which might increase chances of stealing it in case of a successful Cross-Side Scripting attack. It's recommended that cookies storing authentication-related session token are protected by the flag » More...Size: 26 bytesSample value:GA1.2.460528925.1529415873Cookie classification: same-origin session

_gatGoogle Analytics tracking cookie » More...Type: HTTP CookieDomain: cobweb.ieThe cookie is only valid during current browser session and it will be deleted when you close browserhttpOnly This cookie can be read by client-side JavaScript which might increase chances of stealing it in case of a successful Cross-Side Scripting attack. It's recommended that cookies storing authentication-related session token are protected by the flag » More...Size: 1 bytesSample value:1This cookie seems to be a hexadecimal-encoded data. Attempted decoded value:b'\x01'Shannon entropy: 0.00Bit length: 8Cookie classification: same-origin session

_ga 2 years Used to distinguish users._gid 24 hours Used to distinguish users._gat 1 minute Used to throttle request rate. If Google Analytics is deployed via Google Tag Manager, this cookie will be named _dc_gtm_.AMP_TOKEN 30 seconds to 1 year Contains a token that can be used to retrieve a Client ID from AMP Client ID service. Other possible values indicate opt-out, inflight request or an error retrieving a Client ID from AMP Client ID service._gac_ 90 days Contains campaign related information for the user. If you have linked your Google Analytics and AdWords accounts, AdWords website conversion tags will read this cookie unless you opt-out.

ct_checkjsType: HTTP CookieDomain: www.cobweb.ieThe cookie is only valid during current browser session and it will be deleted when you close browserhttpOnly This cookie can be read by client-side JavaScript which might increase chances of stealing it in case of a successful Cross-Side Scripting attack. It's recommended that cookies storing authentication-related session token are protected by the flag

ct_timezoneType: HTTP CookieDomain: www.cobweb.ieThe cookie is only valid during current browser session and it will be deleted when you close browserhttpOnly This cookie can be read by client-side JavaScript which might increase chances of stealing it in case of a successful Cross-Side Scripting attack. It's recommended that cookies storing authentication-related session token are protected by the flagSize: 1 bytesSample value:0This cookie seems to be a hexadecimal-encoded data. Attempted decoded value:b'\x00'Shannon entropy: 0.00Bit length: 8Cookie classification: same-origin session

What is a httpOnly cookie?

HTTP cookies can be created in two ways: either in the HTTP layer, on in the application layer in the DOM using JavaScript. And after they are created, some cookies can be accessed from either layer, depending on the application requirements.

HTTP cookies can be created in a web browser either by the Set-Cookie header in a HTTP response or using JavaScript using the document.cookie property. An example from JavaScript console:

> document.cookie"cookieconsent_status=dismiss; test_cookie=true"The same cookie can be set using a HTTP response header:

Set-Cookie: cookieconsent_status=dismiss; test_cookie=trueThis gives application developers great flexibility in customizing the application behavior to match user preferences — for example, if an user indicated a preference to see the website in French language, the application can set a cookie language=french which the browser will send in all subsequent requests. Upon receiving the cookie, the application will then display content in appropriate language, always returning what the user has chosen to see. The cookie can be read from either the HTTP session (Cookie request header), which is what most server-side applications would do, or client-side using JavaScript, a mode preferred by most AJAX JavaScript-based applications.