| |
fPCGI 2.0 New Features Overview
 |
New Environment
File Capability
- fPcgi 2.0 nows allows you to move the various hidden
control fields such as Field_ddir, Field_base, Field_cmd,
into either the global fpcgi.env file or a document referenced
environment which you can build on the fly with the filePro
processing that, for instance, built the submitting document.
A new hidden field, Field_localenv specifies the
full path to these document referenced environment files.
- A view source on the submitting HTML document no longer
has to to show these hidden fields except for Field_localenv.
- Any of these field directives that begin with Field_
will be added to the flat ascii file fPcgi creates and therefore
will be available to filePro processing. In fact, if you
want to place any fieldname with its value in the localenv
file, you simply add a line to the localenv file such as FIELD
Return=/fpcgidemo.htm
- With the new local envrionment file capability used in
conjunction with the PFNOREMOTECMD and the PFCGIWAITTIME
settings, fPcgi2.0 sets the stage for better protection
from Denial of Service attacks than fPcgi 1.0.
New Global Environment Control Settings
- PFCGIWAITTIME=30 [Added to Unix and Linux versions]
This is time in seconds for fPcgi to wait for the return document before
timing out. The default value is 30
- PFNOREMOTECMD=YES [1, True, On, No, 0, false, Off]
This directive when set will instruct fPcgi not to run any Field_cmd that
might exist in the submitting document or a browser command line that mimicks
a submitting document. In this case, all of the Field_cmds must exist in
the new server-side local environment files.
New Https Capability
- This new version of fpcgi allows you to have fPcgi redirect
the returned output to a secure server using https:// versus httpd://.
Two new hidden control fields Field_returnhttps and Field_httpsprefix are
used to control this feature.
- The return document will be considered to be being sent
as a secure document (https) if the calling page was secure,
or if Field_returnhttps is set (Yes, True, On, or 1).
- If the return document is supposed to be secure, the
return page address is built using either:
(1) the Field_httpsprefix/returnDocumentName if one exists
or
(2)https://SERVER_NAME/returnDocumentName
- If Field_httpsprefix is set it is assumed to be everything
in the address up to the point of the name of the return
document.
New Alias Feature for Control Fields
- fPcgi 2.0 allows you to assign aliases to the various
hidden control fields. This allows other applications such
as Verisign's payflow link for credit card processing to
run fPcgi sequences even though you are not able to specify
new field names when using Verisign.
- Verisign uses USER1, USER2, etc. and allows you to specify
what they should contain when Verisign returns back to filePro
after processing a credit card transaction. Prior to this
new aliasing feature, the developer had to write a return
perl script to run filePro processing. Now you will be able
to alias USER2 to Field_cmd etc. and fPcgi will treat USER2
just like it treats Field_cmd. Typical syntax: ALIAS
USER2=Field_localenv
- The local environment file would contain the Field_cmd
directive and the Aliased fields would contain field or
other application specific variable data that the processing
table specified by the Field_cmd in the local environment
file will use. Please note: You should not Alias
Field_cmd if you want the new security protection provided
by the PFNOREMOTECMD=YES directive, since fPcgi 2.0 will
treat that Alias as if it were Field_cmd and disregard it.
New Default Return File Feature
- A new hidden control field, Field_nohtmlfound,
allows you to specify a static page you want fPcgi to return
in the event, the filePro processing it runs fails to build
a return document.
New Delete Feature for fPcgi flat ascii files
- fPcgi 2.0 nows allows you to specify that the flat files
generated by fPcgi are deleted by fPcgi when it finishes
running a specified series of Field_cmd as per the submitting
document. The default is that it does not delete them as
in fPcgi 1.0. A new hidden field Field_removeflat allows
you to specify whether you want fPcgi to delete the files
or not. fPcgi will also look for the existence of a previously
generated return html document with the same temporary name
and delete it before it runs filePro.
Enhanced fPcgi Logging
- If you specify Field_docid as a hidden field in
your submitting document fPcgi 2.0 will include it all log
entries generated for that document.
- fPcgi now logs Remote User information in the logs. They
include REMOTE_ADDR, REMOTE_HOST, REMOTE_IDENT, REMORE_USER,
and HTTP_USER_AGENT. The usefullness of this information
is dependent on Web server, Web Browser, and operating system
issues.
Remote User Information
- If you specify Field_trackremote=yes as a hidden
field in your submitting document or its corresponding environment
file, fPcgi 2.0 will include Field_remoteaddr, Field_remotehost,
Field_remoteident, Field_remoteuser, and Field_httpuseragent
in the flat ASCII file its generates. This would allow you
to store them in a filePro data base if you want to.
|
|
|
|
