bump VERSION and Changes for CPAN release

Changes

@@ -1,5 +1,10 @@
 Revision history for CGI::Fast
 
+2.12 2016-11-22
+    [DOCUMENTATION]
+    - tweak docs about overriding STDIN due to interference with POST
+      requests (GH #16, thanks to melak)
+
 2.11 2016-11-17
     [FIX]
     - make sure we use CGI::Carp as we depend on it (GH #15, thanks to melak)

README.md

@@ -19,9 +19,8 @@ CGI::Fast - CGI Interface for Fast CGI
 
     $COUNTER = 0;
 
-    # optional, will default to STDOUT, STDIN, STDERR
+    # optional, will default to STDOUT, STDERR
     CGI::Fast->file_handles({
-        fcgi_input_file_handle  => IO::Handle->new,
         fcgi_output_file_handle => IO::Handle->new,
         fcgi_error_file_handle  => IO::Handle->new,
     });
@@ -169,14 +168,13 @@ use CGI::Fast as a drop in replacement like so:
 
 # FILE HANDLES
 
-FCGI defaults to using STDIN, STDOUT, and STDERR as its filehandles - this
+FCGI defaults to using STDOUT and STDERR as its output filehandles - this
 may lead to unexpected redirect of output if you migrate scripts from CGI.pm
 to CGI::Fast. To get around this you can use the file\_handles method, which
 you must do **before** the first call to CGI::Fast->new. For example using
 IO::Handle:
 
     CGI::Fast->file_handles({
-        fcgi_input_file_handle  => IO::Handle->new,
         fcgi_output_file_handle => IO::Handle->new,
         fcgi_error_file_handle  => IO::Handle->new,
     });
@@ -185,6 +183,9 @@ IO::Handle:
         ..
     }
 
+Overriding STDIN using the `fcgi_input_file_handle` key is also possible,
+however doing so is likely to break at least POST requests.
+
 # CAVEATS
 
 I haven't tested this very much.

lib/CGI/Fast.pm

@@ -3,7 +3,7 @@ use strict;
 use warnings;
 use if $] >= 5.019, 'deprecate';
 
-$CGI::Fast::VERSION='2.11';
+$CGI::Fast::VERSION='2.12';
 
 use CGI;
 use CGI::Carp;