URI arguments and reserved keywords

Extbase uses special URI arguments to pass variables to Controller arguments and the framework itself.

Extbase uses a prefixed URI argument scheme that relies on plugin configuration.

For example, the example extension EXT:blog_example would use:

// Linebreaks just for readability.

// Actually, the [] parameters are often URI encoded, so this is emitted:

as the created URI to execute the showAction of the Controller PostController within the plugin BlogList.

The following arguments are evaluated:

Controller action to execute
Controller containing the action
Output format (usually html, can also be json or custom types)
the cHash always gets calculated to validate that the URI is allowed to be called. (see Caching variants - or: What is a "cache hash"?)

Any other argument will be passed along to the controller action and can be retrieved via $this->request->getArgument(). Usually this is auto-wired by the automatic parameter mapping of Extbase.

These URI arguments can also be used for the routing configuration, see Extbase plugin enhancer.

When submitting a HTML <form>, the same URI arguments will be part of a HTTP POST request, with some more special ones:

An array with information of the referring call (subkeys: @extension, @controller, @action,

arguments (hashed), @request (json)

List of properties to be submitted to an action (hashed and secured)

These two keys are also regarded as reserved keywords. Generally, you should avoid custom arguments interfering with either the @... or __... prefix notation.