in reply to Re^5: The most powerful CMS developed in Perl (not spam, sounds that way) (without functions)
in thread The most powerful CMS developed in Perl (not spam, sounds that way)

What web server are you using that magically corrects incorrect Content-Length headers for you without reading the input stream?

You didn't address the data loss or the incorrect parameter separator bugs either, and I just noticed you ignore the encoding of input. Why?

  • Comment on Re^6: The most powerful CMS developed in Perl (not spam, sounds that way) (without functions)
  • Download Code

Replies are listed 'Best First'.
Re^7: The most powerful CMS developed in Perl (not spam, sounds that way) (without functions)
by Anonymous Monk on Mar 15, 2013 at 01:26 UTC
    Re: input length, ref: http://perldoc.perl.org/CGI.html#Avoiding-Denial-of-Service-Attacks, which states such functionality is not enabled by default, the web-server can limit resources for CGI scripts.

    Which data loss 'bug' are you referring to? This code has been running for years now with no data loss?

    Parameter separator bug, I presume you are talking about the lack of '=' also setting the value to 1. This is a feature to cut the URI string down.

    The URI input is parsed using a standard method and is UTF8 compatible; $v =~ s/%(0-9A-Fa-f{2})/chr(hex($1))/eg;

[reply]
      Re: input length

      That says nothing about the Content-Length header. Sure, you could configure your web server to kill the execution of your program after it performs a blocking read for more than 90 seconds, but it wouldn't take much effort at all to DOS your server by sending tiny trivial requests.

      Which data loss 'bug' are you referring to?

      The one where you lose query parameters.

      Parameter separator bug, I presume you are talking about the lack of '=' also setting the value to 1.

      Nope. Read the RFCs.

      The URI input is parsed using a standard method and is UTF8 compatible

      I didn't write "UTF-8". I wrote "encoding". What if, for example, one of your users uses IE on Windows and submits a form with the CP-1252 encoding? Do you know if you handle that correctly? Are you sure that you're decoding characters outside of the ASCII range correctly?

[reply]
[d/l]
        1.the 'encoding' issue can be knocked on the head. Igaro uses utf8 for everything and submits forms over ajax specifically with utf8 encoding set. Although I haven't tested it all languages, it certainly works fine in English and Greek.

        2. No query parameters have yet been lost, so please refer me to the specific RFC which states the method of parsing you refer to?

        3. how can the CGI script block read for ninty seconds if you send a tiny trivial request? CGI does not enable content-length by default, and neither does igaro.

[reply]

In Section Cool Uses for Perl