If there frontend web server used, then CGI executed on backend web server will not be able to detect user's IP/port and is HTTPS used in usual way, because CGI "user" now isn't real user, but frontend web server instead.

In this case usual environment variables REMOTE_ADDR and REMOTE_PORT will contain frontend web server's address, and variable HTTPS will not exists (because frontend will not use https to connect to backend even if user connects to frontend using https).

If you can guarantee only frontend is able to connect to backend, then you can safely trust these X-Real-* headers. In this case you can set frontend_prefix => 'X-Real-' and new() will parse headers with this prefix instead of standard REMOTE_ADDR, REMOTE_PORT and HTTPS variables.

Sometimes POST/PUT request sent to url which also contain some parameters (after '?'). By default these parameters will be ignored, and only parameters sent in HTTP request body (STDIN) will be parsed (to {POST}). If you want to additionally parse parameters from url you should set post_with_get => 1 option (these parameters will be parsed to {GET} and not mixed with parameters in {POST}).

By default only parameters which names ending with '[]' are allowed to have more than one value. These parameters stored in fields {GET}, {POST}, {filename} and {mimetype} as ARRAYREF, while all other parameters stored as SCALAR (only first value for these parameters is stored). If you want to allow more than one value in all parameters you should set keep_all_values => 1 option, and all parameters will be stored as ARRAYREF.

Will contain request parameters. For request methods POST and PUT parameters will be stored in {POST} (if option post_with_get => 1 used then parameters from url will be additionally stored in {GET), for all other methods (HEAD/GET/DELETE/etc.) parameters will be stored in {GET}.

These fields will contain HASHREF with parameter names, which value will depend on keep_all_values option. By default, value for parameters which names ending with '[]' will be ARRAYREF, and for all other SCALAR (only first value for these parameters will be stored if more than one available).

When <INPUT TYPE="FILE"> used to upload files, browser will send uploaded file name and MIME type in addition to file contents. These values will be available in fields {filename} and {mimetype}, which have same format as {POST} field.

Example: submitted form contain parameter "a" with value "5" and parameter "image" with value of file "C:\Images\some.gif" will be parsed to:

1) Web server will check user login/pass, and will provide values for {AUTH_TYPE} and {REMOTE_USER}. In this case {REMOTE_PASS} will contain undef().

2) Your CGI will manually check authentication. Only 'Basic' type of HTTP authentication supported by this module. In this case {AUTH_TYPE} will be set to 'Basic', and {REMOTE_USER} and {REMOTE_PASS} will contain login/pass sent by user, and your CGI should check is they correct. To allow this type of manual authentication you may need to configure .htaccess to force Apache to send HTTP_AUTHORIZATION environment to your CGI/FastCGI script:

These fields will contain copy of %ENV and STDIN contents as they was seen by new(). This is useful to access values in %ENV which doesn't included in other fields of this object, and to manually parse non-standard data in STDIN.

This method shouldn't be called if you modified format of {GET} or {POST} fields.

When called without parameter will return ARRAY with all CGI parameter names, both GET and POST parameter names will be joined.

When called with parameter name will return value of this parameter (from POST parameter if it exists, or from GET if it doesn't exist in POST parameters). All stored values (see keep_all_values option) for this parameter will be returned in ARRAY context, and only first value will be returned in SCALAR context.

Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.