Change history - Ympäristönsuojeluyksikkö - Organisations

jdukpa updated the dataset Tampereen luontopolkureitit
6 years ago

jdukpa updated the dataset Tampereen meluselvitys 2017
6 years ago

jdukpa updated the dataset Tampereen luontopolkurastit
6 years ago

jdukpa updated the dataset Tampereen luonnonmuistomerkit
6 years ago

jdukpa updated the dataset Tampereen meluselvitys 2017
6 years ago

jdukpa created the dataset Tampereen meluselvitys 2017
6 years ago

jdukpa updated the dataset Tampereen luontopolkurastit
6 years ago

jdukpa updated the dataset Tampereen luontopolkureitit
6 years ago

jdukpa updated the dataset Tampereen luonnonmuistomerkit
6 years ago

Name	Hostname	Vendor	Expiry
PHPSESSID	data.tampere.fi		Session
Cookie generated by applications based on the PHP language. This is a general purpose identifier used to maintain user session variables. It is normally a random generated number, how it is used can be specific to the site, but a good example is maintaining a logged-in status for a user between pages.
_GRECAPTCHA	www.google.com	Google	180 days
Used by Google reCaptcha for risk analysis
cookiehub	.data.tampere.fi	CookieHub	365 days
Used by CookieHub to store information about whether visitors have given or declined the use of cookie categories used on the site.
wordpress_test_cookie	data.tampere.fi	Wordpress	Session
Used by Wordpress to check if the cookies are enabled on the browser.

Name	Hostname	Expiry
pll_language	data.tampere.fi	365 days
This cookie is used to remember the language selected by the user when he comes back to visit again the website by Polylang
AWSALB	data.tampere.fi	7 days
Amazon Web Services cookie. This cookie enables us to allocate server traffic to make the user experience as smooth as possible. A so-called load balancer is used to determine which server currently has the best availability. The information generated cannot identify you as an individual.
AWSALBCORS	data.tampere.fi	7 days
Amazon Web Services cookie. This cookie enables us to allocate server traffic to make the user experience as smooth as possible. A so-called load balancer is used to determine which server currently has the best availability. The information generated cannot identify you as an individual.