That's not really a good way to do it. What happens when a new version of CGI::Application comes out that makes a change in query()? The code above will break. Instead, call the real query() to do the work using SUPER:
package CGI::Application::POST_MAX;
use base 'CGI::Application';
sub query {
my $self = shift;
if (not exists $self->{__POST_MAX_SET__}) {
$CGI::POST_MAX=1024 * 100; # max 100K posts
$self->{__POST_MAX_SET__} = 1;
}
return $self->SUPER::query(@_);
}
1;
Of course, this still isn't 100% future-proof since it will break if a future version of CGI::Application uses the hash key "__POST_MAX_SET__" but I'd consider that an acceptable risk.
But is this even necessary? Can't you just put this at the top of your CGI::Application class:
BEGIN { $CGI::POST_MAX = 1020 * 100; }
-sam
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
Read Where should I post X? if you're not absolutely sure you're posting in the right place.
Please read these before you post! —
Posts may use any of the Perl Monks Approved HTML tags:
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
| |
For: |
|
Use: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.