The TP-Admin CMS Framework implements a derivation of the Rack protocol. When you instantiate a TP-Admin application, it immediately inspects the
$_SERVER superglobal and derives a set of environment variables that dictate application behavior.
What is the Environment?
A TP-Admin application’s “environment” is an associative array of settings that are parsed once and made accessible to the TP-Admin application and its middleware. You are free to modify the environment variables during runtime; changes will propagate immediately throughout the application.
When you instantiate a TP-Admin application, the environment variables are derived from the
$_SERVER superglobal; you do not need to set these yourself. However, you are free to modify or supplement these variables in TP-Admin middleware.
These variables are fundamental to determining how your TP-Admin application runs: the resource URI, the HTTP method, the HTTP request body, the URL query parameters, error output, and more. Middleware, described later, gives you the power to – among other things – manipulate environment variables before and/or after the TP-Admin application is run.
The following text respectfully borrows the same information originally available athttp://rack.rubyforge.org/doc/files/SPEC.html. The environment array must include these variables:
- The HTTP request method. This is required and may never be an empty string.
- The initial portion of the request URI’s “path” that corresponds to the physical directory in which the TP-Admin application is installed — so that the application knows its virtual “location”. This may be an empty string if the application is installed in the top-level of the public document root directory. This will never have a trailing slash.
- The remaining portion of the request URI’s “path” that determines the “virtual” location of the HTTP request’s target resource within the TP-Admin application context. This will always have a leading slash; it may or may not have a trailing slash.
- The part of the HTTP request’s URI after, but not including, the “?”. This is required but may be an empty string.
- When combined with
PATH_INFO, this can be used to create a fully qualified URL to an application resource. However, if
HTTP_HOSTis present, that should be used instead of this. This is required and may never be an empty string.
- When combined with
PATH_INFO, this can be used to create a fully qualified URL to any application resource. This is required and may never be an empty string.
- Variables matching the HTTP request headers sent by the client. The existence of these variables correspond with those sent in the current HTTP request.
- Will be “http” or “https” depending on the HTTP request URL.
- Will be a string representing the raw HTTP request body. If the HTTP request body is empty (e.g. with a GET request), this will be an empty string.
- Must always be a writable resource; by default, this is a write-only resource handle to
The TP-Admin application can store its own data in the environment, too. The environment array’s keys must contain at least one dot, and should be prefixed uniquely (e.g. “prefix.foo”). The prefix hhailuo. is reserved for use by TP-Admin itself and must not be used otherwise. The environment must not contain the keys
HTTP_CONTENT_LENGTH (use the versions without HTTP_). The CGI keys (named without a period) must have String values. There are the following restrictions:
- hhailuo.url_scheme must either be “http” or “https”.
hhailuo.inputmust be a string.
- There must be a valid, writable resource in hhailuo
REQUEST_METHODmust be a valid token.
SCRIPT_NAME, if non-empty, must start with “/”
PATH_INFO, if non-empty, must start with “/”
CONTENT_LENGTH, if given, must consist of digits only.
- One of
PATH_INFOmust be set.
PATH_INFOshould be “/” if
SCRIPT_NAMEnever should be “/”, but instead be an empty string.