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

...

Cookies are little files a web server places at the client side which can be queried by the server later. In most cases these are used for harmless functions - after all, HTTP does not create a "session" but works rather like a mail exchange. HTTP consists of independent messages going back and forth between sender and receiver and if one wants to provide lasting context (this is what sets apart "sessions" from "messages") either the web server has to remember it - which would lead to exhaustion of resources on the server side in a very short time - or the server has to have a way to offload that to the client. This was the original rationale for creating cookies and in general storing web content on the client side.
First. let me help you clarify.

Cookies are generally not "queried" by a server. Cookies are sent to the server with each page (that belong to the same cookie domain) as part of the standard HTTP request.

If you open any web dev tool, like Google Chrome Web Dev Tools (but it is the same with each major browser), you will see the cookies are sent with each page, not requested by the server.

Sorry, I just wanted to be technically correct.
 
KCOOKIEJAR4(8)							 KDE User's Manual						    KCOOKIEJAR4(8)

NAME
kcookiejar4 - KDE HTTP cookie daemon SYNOPSIS
kcookiejar4 [--help] [Generic-options] [Qt-options] [KDE-options] [--shutdown] [--remove domain] [--remove-all] [--reload-config] DESCRIPTION
kcookiejar4 handles the HTTP cookies providing a D-BUS service to store/retrieve/clean cookies. GENERIC OPTIONS
--author Show author information. --help Show help about options. --help-all Show all options. --help-kde Show KDE specific options. --help-qt Show Qt specific options. --license Show license information. -v--version Show version information APPLICATION OPTIONS
--shutdown Shut down cookie jar and the D-BUS service. --remove domain Removes cookies for domain from the cookie jar. --remove-all Removes all the cookies from the cookie jar. --reaload-config Reloads the configuration file. USAGE
KDE web browser konqueror uses kcookiejar4 for storing and managing cookies using the D-Bus service kcookiejar4 provides. When kcookiejar4 is started without parameters, it provides a D-BUS service to handle HTTP cookies. When kcookiejar4 is started with some parameters, it does additional tasks to the cookies jar it provides, like removing the cookies from one domain. SEE ALSO
kdeoptions(7), qtoptions(7) BUGS
There are probably tons of bugs. Use bugs.kde.org[1] to report them. AUTHORS
Waldo Bastian <bastian@kde.org> Author. Dawit Alemayehu <adawit@kde.org> Author. NOTES
1. bugs.kde.org http://bugs.kde.org 0.01.01 2008-10-14 KCOOKIEJAR4(8)
All times are GMT -4. The time now is 08:18 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy