Sponsored Content
The Lounge What is on Your Mind? Individual Risk Management (Personal IT Security) and Browser Cache Management Post 303033322 by Neo on Wednesday 3rd of April 2019 07:56:15 AM
Old 04-03-2019
Quote:
Originally Posted by bakunin

You asked for a scenario where this might pose a risk to the user: let us say i search Google for ways to overcome personal debt repeatedly. If one of the "advertisement partners" of Google is the next bank and if Google is able to identify me across sessions i may well have lowered my credit rating effectively by doing that research - even if it might not even be for me. Given, that is a constructed example and includes a lot of conjecture - but the girl getting advertisement for baby food before even her parents were aware of her pregnancy was real. It is not a lot different (not in scope and definitely not in technical background) from what i presented here.
Yes, that first example is "constructed" and not really realistic.

The second is a real example, but that example is not because of "cookies and caches"... it was because the girl had made purchases with Target and so Target (a retail chain in the US) sent her a paper flyer in the mail based on her purchases.

Quote:
Pole identified 25 products that when purchased together indicate a women is likely pregnant. The value of this information was that Target could send coupons to the pregnant woman at an expensive and habit-forming period of her life.
Neither of your examples are related to clearing cookies and caches.

The first is just a fantasy based without facts or details.

The second is well documented NOT to be related to cookies or web caches, but is related to the computer records of the purchases of the girl in the story. The article ends with an apology:

Quote:
On the phone, though, the father was somewhat abashed. "I had a talk with my daughter," he said. "It turns out there's been some activities in my house I haven't been completely aware of. She's due in August. I owe you an apology."
Can we please stick to the facts of "cookies" and "caches" which you advised people to clear "for their own good".

Neither of the scenarios you posted are relevant to that. I am sorry to inform!!

On the other hand, even if the girl in the "real story" above cleared her cookies and cache, she would have still got the coupons because she was targeted (marketing) because of her purchase history with the company in their database, not because of "cookies" or "caches" in browsers.
 
Mojo::Message::Request(3pm)				User Contributed Perl Documentation			       Mojo::Message::Request(3pm)

NAME
Mojo::Message::Request - HTTP 1.1 request container SYNOPSIS
use Mojo::Message::Request; # Parse my $req = Mojo::Message::Request->new; $req->parse("GET /foo HTTP/1.0x0ax0d"); $req->parse("Content-Length: 12x0ax0dx0ax0d"); $req->parse("Content-Type: text/plainx0ax0dx0ax0d"); $req->parse('Hello World!'); say $req->body; # Build my $req = Mojo::Message::Request->new; $req->url->parse('http://127.0.0.1/foo/bar'); $req->method('GET'); say $req->to_string; DESCRIPTION
Mojo::Message::Request is a container for HTTP 1.1 requests as described in RFC 2616. EVENTS
Mojo::Message::Request inherits all events from Mojo::Message. ATTRIBUTES
Mojo::Message::Request inherits all attributes from Mojo::Message and implements the following new ones. "env" my $env = $req->env; $req = $req->env({}); Direct access to the "CGI" or "PSGI" environment hash if available. # Check CGI version my $version = $req->env->{GATEWAY_INTERFACE}; # Check PSGI version my $version = $req->env->{'psgi.version'}; "method" my $method = $req->method; $req = $req->method('POST'); HTTP request method, defaults to "GET". "url" my $url = $req->url; $req = $req->url(Mojo::URL->new); HTTP request URL, defaults to a Mojo::URL object. my $foo = $req->url->query->to_hash->{foo}; METHODS
Mojo::Message::Request inherits all methods from Mojo::Message and implements the following new ones. "clone" my $clone = $req->clone; Clone request if possible, otherwise return "undef". "cookies" my $cookies = $req->cookies; $req = $req->cookies(Mojo::Cookie::Request->new); $req = $req->cookies({name => 'foo', value => 'bar'}); Access request cookies, usually Mojo::Cookie::Request objects. say $req->cookies->[1]->value; "fix_headers" $req = $req->fix_headers; Make sure request has all required headers for the current HTTP version. "is_secure" my $success = $req->is_secure; Check if connection is secure. "is_xhr" my $success = $req->is_xhr; Check "X-Requested-With" header for "XMLHttpRequest" value. "param" my @names = $req->param; my $foo = $req->param('foo'); my @foo = $req->param('foo'); Access "GET" and "POST" parameters. Note that this method caches all data, so it should not be called before the entire request body has been received. "params" my $p = $req->params; All "GET" and "POST" parameters, usually a Mojo::Parameters object. say $req->params->param('foo'); "parse" $req = $req->parse('GET /foo/bar HTTP/1.1'); $req = $req->parse(REQUEST_METHOD => 'GET'); $req = $req->parse({REQUEST_METHOD => 'GET'}); Parse HTTP request chunks or environment hash. "proxy" my $proxy = $req->proxy; $req = $req->proxy('http://foo:bar@127.0.0.1:3000'); $req = $req->proxy(Mojo::URL->new('http://127.0.0.1:3000')); Proxy URL for request. # Disable proxy $req->proxy(0); "query_params" my $p = $req->query_params; All "GET" parameters, usually a Mojo::Parameters object. say $req->query_params->to_hash->{'foo'}; SEE ALSO
Mojolicious, Mojolicious::Guides, <http://mojolicio.us>. perl v5.14.2 2012-09-05 Mojo::Message::Request(3pm)
All times are GMT -4. The time now is 06:41 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy