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
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.
XMLRPC::Transport::HTTP(3pm)				User Contributed Perl Documentation			      XMLRPC::Transport::HTTP(3pm)

XMLRPC::Transport::HTTP - Server/Client side HTTP support for XMLRPC::Lite SYNOPSIS
Client use XMLRPC::Lite proxy => 'http://localhost/', # proxy => 'http://localhost/cgi-bin/xmlrpc.cgi', # local CGI server # proxy => 'http://localhost/', # local daemon server # proxy => 'http://login:password@localhost/cgi-bin/xmlrpc.cgi', # local CGI server with authentication ; print getStateName(1); CGI server use XMLRPC::Transport::HTTP; my $server = XMLRPC::Transport::HTTP::CGI -> dispatch_to('methodName') -> handle ; Daemon server use XMLRPC::Transport::HTTP; my $daemon = XMLRPC::Transport::HTTP::Daemon -> new (LocalPort => 80) -> dispatch_to('methodName') ; print "Contact to XMLRPC server at ", $daemon->url, " "; $daemon->handle; DESCRIPTION
This class encapsulates all HTTP related logic for a XMLRPC server, independent of what web server it's attached to. If you want to use this class you should follow simple guideline mentioned above. PROXY SETTINGS You can use any proxy setting you use with LWP::UserAgent modules: XMLRPC::Lite->proxy('http://endpoint.server/', proxy => ['http' => 'http://my.proxy.server']); or $xmlrpc->transport->proxy('http' => 'http://my.proxy.server'); should specify proxy server for you. And if you use "HTTP_proxy_user" and "HTTP_proxy_pass" for proxy authorization SOAP::Lite should know how to handle it properly. COOKIE-BASED AUTHENTICATION use HTTP::Cookies; my $cookies = HTTP::Cookies->new(ignore_discard => 1); # you may also add 'file' if you want to keep them between sessions my $xmlrpc = XMLRPC::Lite->proxy('http://localhost/'); $xmlrpc->transport->cookie_jar($cookies); Cookies will be taken from response and provided for request. You may always add another cookie (or extract what you need after response) with HTTP::Cookies interface. You may also do it in one line: $xmlrpc->proxy('http://localhost/', cookie_jar => HTTP::Cookies->new(ignore_discard => 1)); COMPRESSION XMLRPC::Lite provides you option for enabling compression on wire (for HTTP transport only). Both server and client should support this capability, but this logic should be absolutely transparent for your application. Server will respond with encoded message only if client can accept it (client sends Accept-Encoding with 'deflate' or '*' values) and client has fallback logic, so if server doesn't understand specified encoding (Content-Encoding: deflate) and returns proper error code (415 NOT ACCEPTABLE) client will repeat the same request not encoded and will store this server in per-session cache, so all other requests will go there without encoding. Having options on client and server side that let you specify threshold for compression you can safely enable this feature on both client and server side. Compression will be enabled on client side IF: threshold is specified AND size of current message is bigger than threshold AND module Compress::Zlib is available. Client will send header 'Accept-Encoding' with value 'deflate' if threshold is specified AND module Compress::Zlib is available. Server will accept compressed message if module Compress::Zlib is available, and will respond with compressed message ONLY IF: threshold is specified AND size of current message is bigger than threshold AND module Compress::Zlib is available AND header 'Accept-Encoding' is presented in request. DEPENDENCIES
Crypt::SSLeay for HTTPS/SSL HTTP::Daemon for XMLRPC::Transport::HTTP::Daemon Apache, Apache::Constants for XMLRPC::Transport::HTTP::Apache SEE ALSO
See ::CGI, ::Daemon and ::Apache for implementation details. See examples/XMLRPC/* for examples. COPYRIGHT
Copyright (C) 2000-2001 Paul Kulchenko. All rights reserved. This library is free software; you can redistribute it and/or modify it under the same terms as Perl itself. AUTHOR
Paul Kulchenko (paulclinger@yahoo.com) perl v5.12.4 2011-08-18 XMLRPC::Transport::HTTP(3pm)

Featured Tech Videos

All times are GMT -4. The time now is 06:37 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy