use MRO::Compat;
use Catalyst::Utils ();
-our $VERSION = "0.16";
+our $VERSION = "0.17";
has _deleted_session_id => ( is => 'rw' );
If this attribute B<set to 0> the cookie will not have the secure flag.
If this attribute B<set to 1> (or true for backward compatibility) - the cookie
-send by the server to the client will got the secure flag that tells the browser
-to send this cookies back to the server only via HTTPS.
+sent by the server to the client will get the secure flag that tells the browser
+to send this cookie back to the server only via HTTPS.
-If this attribute B<set to 2> then the cookie will got the secure flag only if
+If this attribute B<set to 2> then the cookie will get the secure flag only if
the request that caused cookie generation was sent over https (this option is
-not good if you are mixing https and http in you application).
+not good if you are mixing https and http in your application).
-Default vaule is 0.
+Default value is 0.
=item cookie_httponly
Default value is 1.
-Note1: Many peole are confused by the name "HTTPOnly" - it B<does not mean>
+Note1: Many people are confused by the name "HTTPOnly" - it B<does not mean>
that this cookie works only over HTTP and not over HTTPS.
-Note2: This paramater requires Catalyst::Runtime 5.80005 otherwise is skipped.
+Note2: This parameter requires Catalyst::Runtime 5.80005 otherwise is skipped.
=item cookie_path
=head1 COPYRIGHT
-Copyright (c) 2005, Yuval Kogman C<< <nothingmuch@woobling.org> >>
+Copyright (c) 2005 - 2009
+the Catalyst::Plugin::Session::State::Cookie L</AUTHORS> and L</CONTRIBUTORS>
+as listed above.
=head1 LICENSE