/ 
Jifty-0.60321
River stage two • 33 direct dependents • 33 total dependents
/ Jifty::Script::Action
Security Advisories (4)
CPANSA-Jifty-2011-01 (2011-03-17)

The path as passed in the fragment request data structure was used verbatim in the dispatcher and other locations. This possibly allowed requests to walk around ACLs by requesting '/some/safe/place/../../../dangerous' as a fragment.

CPANSA-Jifty-2009-01 (2009-04-09)

The REST plugin would let you call any method on the model.

CPANSA-Jifty-2008-01 (2009-04-08)

Allowed all actions on GET.

CPANSA-Jifty-2006-01 (2006-07-06)

Jifty did not protect users against a class of remote data access vulnerability. If an attacker knew the structure of your local filesystem and you were using the "standalone" webserver in production, the attacker could gain read only access to local files.

NAME

Jifty::Script::Action - Add an action class to your Jifty application

DESCRIPTION

This creates a skeleton of a new action class for your jifty application, complete with a skeleton of a test suite for it, as well.

API

options

There are only two possible options to this script:

--name NAME (required)

Name of the action class.

--force

By default, this will stop and warn you if any of the files it is going to write already exist. Passing the --force flag will make it overwrite the files.

run

Creates a skeleton file under lib/ApplicationClass/Action/Action, as well as a skeleton tests file.

NAME

@{[$appclass]}::Action::@{[$action]}

arguments

take_action

report_success

DESCRIPTION

A (very) basic test harness for the $action action.