'Test' 1st Party Cookie Value

The 'test' cookie is set on gingerandpole.com and is therefore considered a 1st Party Cookie on this page

The cookie with name 'test' and set on domain=gingerandpole.com has the following values:


Scenario 1: BBC < Partner (Using Client Side JS Or Server Side PHP)

The user lands on .com and gets a cookie set on .com (BBC). User then moves to .co.uk (partner)

  1. Firstly, clear any left over cookies:
  2. Second, set the cookie on .com (BBC) using JS (client side tech): or using Server Side (PHP)
  3. Now hop over to .co.uk (partner) and you will see that .co.uk cannot read this cookie at all.

Conclusion 1: Cookies set on .com using client side or server side tech cannot be read on .co.uk

Scenario 2: Partner > BBC (Using Server Side PHP)

The user lands on .co.uk (partner) and gains a cookie by server side tech set to .com (BBC) domain. This is a 3rd party cookie.

  1. Firstly, clear any left over cookies:
  2. Now hop over to .co.uk and follow the scenario 3 instructions there

Conclusion 2: A 3rd party cookie can be set by a server side script requested from .com (BBC) but it cannot be viewed by either server side tech from .co.uk (Partner) or ANY client side script from any origin. This cookie can be read by server side script on .com (BBC) only.

Scenario 3: Partner only (Using Server Side PHP)

Follow these steps to set a 3rd party cookie with the domain of .com, but actually set on a .co.uk page

  1. Firstly, clear any left over cookies:
  2. Now hop over to .co.uk and follow the scenario 3 instructions there

Conclusion 3:As per conclusion 2, however you will note the cookie value does not change when the user browses to other pages on .co.uk (partner).


All Possible User Actions

To set the test cookie on gingerandpole.com using javascript:
the js code run is: document.cookie = "test=value as set by js code on gingerandpole.com; domain=.gingerandpole.com; expires=Wed, 06 Jul 2016 16:30:13 GMT; path=/"

To set the test cookie on gingerandpole.com using server side tech: page will reload


actual js code run is: document.cookie = "test=a;expires=Thu, 01 Jan 1970 00:00:01 GMT;domain=.gingerandpole.com; path=/";

Notes

1 This value could be [NOT SET] even if the server side script has set the test cookie using a page reload. The cookie value is only available to the server side if it is sent with an HTTP request. So, if the cookie is blank when the request is sent, the value here will also be blank even if the server side populates the cookie itself. To see this cookie value populated here, you may have to reload the page again.

Further Info

The server side script (gingerandpole.com/index.php) had the following cookies available to it when it was requested:

array(0) {
}