Classe: THttpRequest  - X-Ref

THttpRequest class

THttpRequest provides storage and access scheme for user request sent via HTTP.
It also encapsulates a uniform way to parse and construct URLs.

User post data can be retrieved from THttpRequest by using it like an associative array.
For example, to test if a user supplies a variable named 'param1', you can use,
<code>
if(isset($request['param1'])) ...
// equivalent to:
// if($request->contains('param1')) ...
</code>
To get the value of 'param1', use,
<code>
$value=$request['param1'];
// equivalent to:
//   $value=$request->itemAt('param1');
</code>
To traverse the user post data, use
<code>
foreach($request as $name=>$value) ...
</code>
Note, POST and GET variables are merged together in THttpRequest.
If a variable name appears in both POST and GET data, then POST data
takes precedence.

To construct a URL that can be recognized by Prado, use {@link constructUrl()}.
The format of the recognizable URLs is determined according to
{@link setUrlManager UrlManager}. By default, the following two formats
are recognized:
<code>
/index.php?ServiceID=ServiceParameter&Name1=Value1&Name2=Value2
/index.php/ServiceID,ServiceParameter/Name1,Value1/Name2,Value2
</code>
The first format is called 'Get' while the second 'Path', which is specified
via {@link setUrlFormat UrlFormat}. For advanced users who want to use
their own URL formats, they can write customized URL management modules
and install the managers as application modules and set {@link setUrlManager UrlManager}.

The ServiceID in the above URLs is as defined in the application configuration
(e.g. the default page service's service ID is 'page').
As a consequence, your GET variable names should not conflict with the service
IDs that your application supports.

THttpRequest also provides the cookies sent by the user, user information such
as his browser capabilities, accepted languages, etc.

By default, THttpRequest is registered with {@link TApplication} as the
request module. It can be accessed via {@link TApplication::getRequest()}.

Classe: THttpCookieCollection  - X-Ref

THttpCookieCollection class.

THttpCookieCollection implements a collection class to store cookies.
Besides using all functionalities from {@link TList}, you can also
retrieve a cookie by its name using either {@link findCookieByName} or
simply:
<code>
$cookie=$collection[$cookieName];
</code>

Classe: THttpCookie  - X-Ref

THttpCookie class.

A THttpCookie instance stores a single cookie, including the cookie name, value,
domain, path, expire, and secure.

Classe: TUri  - X-Ref

TUri class

TUri represents a URI. Given a URI
http://joe:whatever@example.com:8080/path/to/script.php?param=value#anchor
it will be decomposed as follows,
- scheme: http
- host: example.com
- port: 8080
- user: joe
- password: whatever
- path: /path/to/script.php
- query: param=value
- fragment: anchor

Classe: THttpRequestUrlFormat  - X-Ref

THttpRequestUrlFormat class.
THttpRequestUrlFormat defines the enumerable type for the possible URL formats
that can be recognized by {@link THttpRequest}.

The following enumerable values are defined:
- Get: the URL format is like /path/to/index.php?name1=value1&name2=value2...
- Path: the URL format is like /path/to/index.php/name1,value1/name2,value2...