To add to Rolfs post you can do something like:
<emit source="scopes" filter-exclude="scope=modvar">
<h3>&_.scope;</h3>
<emit source="values" from-scope="&_.scope;">
&_.index; = &_.value;<br/>
</emit>
</emit>
to see all available rxml-vars in a pageload.
Somehow I got the "modvar" scope from emit scopes and emitting that scope gave
me a http500 (hence the manual omission of that scope above)
/Peter
----- Original Message ----
From: Rolf Johansson <[email protected]>
To: Peter Ohlerich <[email protected]>
Cc: Roxen mailing list <[email protected]>
Sent: Mon, March 28, 2011 10:08:51 AM
Subject: Re: Just a question about Request-Variables
On Mon, 28 Mar 2011, Peter Ohlerich wrote:
> A user aked me, if there exists a method to work with the request
> variables in Roxen like the $_REQUEST array in PHP. I did not find the
> information in the docs, so I ask here: can the information of a
> request be queried via RXML like the $_REQEST array in PHP? There's no
> need to have all infos in one associative array, just a way to access
> all infos.
Depends on what you mean by request. All POST and GET parameters go into the
"form" scope, for example "&form.test;" for parameter "test". Cookies goes into
the "cookie" scope, and request headers into "request-header" (and some of
these
are also in the "client" scope, like user-agent, host etc).
Search docs.roxen.com for "form scope", "cookie scope" and so on.
/Rolf
