Loading ...
Sorry, an error occurred while loading the content.

RE: [PBML] 3 Great Mysteries of Perl (to me)

Expand Messages
  • Nathan.Jeffrey@dhs.vic.gov.au
    I m pretty sure that POST and GET are equally as insecure as easch other. I mean, unless you re using SSL, you could snoop all the info right off the wire
    Message 1 of 4 , Sep 26, 2002
    • 0 Attachment
      I'm pretty sure that POST and GET are equally as insecure as easch other.
      I mean, unless you're using SSL, you could snoop all the info right off
      the wire anyway :-)

      POST allows for slightly stingier web servers to be a little more
      pedantic, by only passing URLs of a certain length. This is all my buggy
      memory, so YMMV, as usual.


      "Charles K. Clarkson" <cclarkson@...>
      27/09/2002 03:24 PM
      Please respond to perl-beginner

      To: <perl-beginner@yahoogroups.com>
      Subject: RE: [PBML] 3 Great Mysteries of Perl (to me)

      Will [mailto:self_deprecated@...] wrote:

      : 2.) This one is a query string thing that I never
      : understood exactly. Like I know what a query string
      : is, and I know that the query string starts with the ?
      : after the script's name, and I know what the
      : name=value pairs represent, and that the name=value
      : pairs are separated by an &, but what I dont get is
      : why sometimes name=value pairs do and dont appear in
      : the query string (even though it would seem variables
      : are being used in a script). Can someone explain why
      : this might be the case?

      What you have described is the GET method.
      The POST method allows more information to be
      sent. It uses an HTTP transaction to transfer
      data. I think(?) it POST is also more secure than
      GET. The RFC allows both methods to be used
      simultaneously. In a html form you can specify
      GET or POST in the method element. CGI.pm
      defaults to POST.

      RFC's are maintained at: http://www.rfc-editor.org/

      : 3.) The third great mystery is the use of semicolons
      : in query strings. It seems the majority of the time
      : they arent used, but I have seen a few instances where
      : they have been used, like this:
      : http://www.snake.net/cgi-bin/todo4.pl?choice=edit;id=14
      : Is there a reason why the author of this script/query
      : string (Paul DuBois) would have chosen to use
      : semicolons like that? It seems confusing to me, and I
      : havent been able to locate any info on it in the book.

      Semi-colons and ampersands can be used
      interchangeably. I think(?) the semi-colon was
      introduced in HTTP 1.1 and that HTTP 0.9 and
      1.0 used the ampersand.


      Charles K. Clarkson
      Head Bottle Washer,
      Clarkson Energy Homes, Inc.
      Small commercial and residential rehabilitation specialists.

      254 968-8328

      CJ Web Work - Solutions for Real Estate Investors.
      972 216-4952

      CJ Web Hosting - Affordable Hosting - Custom Accounts.
      254 968-8328

      Unsubscribing info is here:

      Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/


      This email contains confidential information intended only for the person named above and may be subject to legal privilege. If you are not the intended recipient, any disclosure, copying or use of this information is prohibited. The Department provides no guarantee that this communication is free of virus or that it has not been intercepted or interfered with. If you have received this email in error or have any other concerns regarding its transmission, please notify Postmaster@...
    Your message has been successfully submitted and would be delivered to recipients shortly.