Anyone has an idea how to fix this ?

Sure, as documented :)

$ perl -we " m// "
Use of uninitialized value $_ in pattern match (m//) at -e line 1.

$ perl -Mdiagnostics -we " m// "
Use of uninitialized value $_ in pattern match (m//) at -e line 1 (#1)
    (W uninitialized) An undefined value was used as if it were alread
+y
    defined.  It was interpreted as a "" or a 0, but maybe it was a mi
+stake.
    To suppress this warning assign a defined value to your variables.

    To help you figure out what was undefined, perl will try to tell y
+ou the
    name of the variable (if any) that was undefined. In some cases it
+ cannot
    do this, so it also tells you what operation you used the undefine
+d value
    in.  Note, however, that perl optimizes your program and the opera
+tion
    displayed in the warning may not necessarily appear literally in y
+our
    program.  For example, "that $foo" is usually optimized into "that
+ "
    . $foo, and the warning will refer to the concatenation (.) operat
+or,
    even though there is no . in your program.
[download]

you can either make sure whatever variable you're matching against is defined, or silence those warnings, your choice

See also

http://perl.apache.org/docs/1.0/guide/porting.html

CGI::Application/ http://cgi-app.org/ can help you organize your program , as could mojo / dancer / catalyst