CGI::Session::Tutorial

CGI::Session::Tutorial is an extended CGI::Session manual.
Download

CGI::Session::Tutorial Ranking & Summary

Advertisement

  • Rating:
  • License:
  • Perl Artistic License
  • Price:
  • FREE
  • Publisher Name:
  • Mark Stosberg
  • Publisher web site:
  • http://search.cpan.org/~mgraham/CGI-Application-Plugin-FillInForm-1.14/lib/CGI/Application/Plugin/FillInForm.pm

CGI::Session::Tutorial Tags


CGI::Session::Tutorial Description

CGI::Session::Tutorial is an extended CGI::Session manual. CGI::Session::Tutorial is an extended CGI::Session manual.STATE MAINTENANCE OVERVIEWSince HTTP is a stateless protocol, each subsequent click to a web site is treated as new request by the Web server. The server does not relate a visit with a previous one, thus all the state information from the previous requests are lost. This makes creating such applications as shopping carts, web sites requiring users to authenticate, impossible. So people had to do something about this despair situation HTTP was putting us in.For our rescue come such technologies as HTTP Cookies and QUERY_STRINGs that help us save the users' session for a certain period. Since HTTP Cookies and QUERY_STRINGs alone cannot take us too far (RFC 2965, Section 5, "Implementation Limitations"), several other libraries have been developed to extend their capabilities and promise a more reliable solution. CGI::Session is one of them.Before we discuss this library, let's look at some alternative solutions.COOKIECookie is a piece of text-information that a web server is entitled to place in the user's hard disk, assuming a user agent (such as Internet Explorer, Mozilla, etc) is compatible with the specification. After the cookie is placed, user agents are required to send these cookies back to the server as part of the HTTP request. This way the server application ( CGI, for example ) will have a way of relating previous requests by the same user agent, thus overcoming statelessness of HTTP.Although HTTP Cookies seem to be promising solution for the statelessness of HTTP, they do carry certain limitations, such as limited number of cookies per domain and per user agent and limited size on each cookie. User Agents are required to store at least 300 cookies at a time, 20 cookies per domain and allow 4096 bytes of storage for each cookie. They also rise several Privacy and Security concerns, the lists of which can be found on the sections 6-"Privacy" and 7-"Security Considerations" of RFC 2965.QUERY STRINGQuery string is a string appended to URL following a question mark (?) such as: http://my.dot.com/login.cgi?user=sherzodr;password=top-secretAs you probably guessed, it can also help you pass state information from a click to another, but how secure is it do you think, considering these URLs tend to get cached by most of the user agents and also logged in the servers access log, to which everyone can have access. Requirements: · Perl


CGI::Session::Tutorial Related Software