|
HTML::Embperl - Building dynamic Websites with Perl |
HTML::Embperl - Building dynamic Websites with Perl
Embperl is a Perl extension module which gives you the power to embed Perl code directly in your HTML documents (like server-side includes for shell commands).
If building more than a single page, you may also want to take a look at ``perldoc EmbperlObject'' which lets you build your website out of small reusable objects. Additionally, ``perldoc HTML::Embperl::Mail'' allows you to send the resulting page via email.
Embperl can operate in one of four modes:
Converts an HTML file with embedded Perl statements into a standard HTML file.
embpexec.pl [-o outputfile] [-l logfile] [-d debugflags] htmlfile [query_string]
embpexec.bat [-o outputfile] [-l logfile] [-d debugflags] htmlfile [query_string]
Use embpexec.pl on Unix systems and embpexec.bat on Win32 systems.
Instead of a file being sent directly by the web server, the document is processed by the CGI script and the result is sent to the client.
embpcgi.pl
embpcgi.bat
Use embpcgi.pl on Unix systems and embpcgi.bat on Win32 systems. You can also run Embperl with FastCGI, in this case use embpfastcgi.pl as cgi script. You must have FCGI.pm installed.
If embpcgi.pl/embpcgi.bat is invoked without any parameters and the
environment variable PATH_TRANSLATED is set, it runs itself as a CGI
script. This means that form data is taken either from the
environment variable QUERY_STRING or from stdin, depending on whether
or not CONTENT_LENGTH is set. (This will be set by the web server
depending on whether the request method is GET or POST). Input is
taken from the file pointed to by PATH_TRANSLATED and the output is
send to stdout. The logfile is generated at its default location,
which is configurable via the environment variable EMBPERL_LOG.
To use this mode you must copy embpcgi.pl to your cgi-bin directory. You can invoke it with the URL http://www.domain.xyz/cgi-bin/embpcgi.pl/url/of/your/document.
The /url/of/your/document will be passed to Embperl by the web server. Normal processing (aliasing, etc.) takes place before the URI makes it to PATH_TRANSLATED.
If you are running the Apache httpd, you can also define embpcgi.pl as a handler for a specific file extension or directory.
Example of Apache srm.conf:
<Directory /path/to/your/html/docs>
Action text/html /cgi-bin/embperl/embpcgi.pl
</Directory>
NOTE 1: For security reasons, embpexec.pl must not be used as a CGI script anymore!
NOTE 2: CGI Scripts are not so secure. You should consider using EMBPERL_ALLOW to restrict access.
This works like the CGI-Script, but with the advantage that the script
is compiled only once at server startup, where other one-time actions
(such as opening files and databases) can take place. This will
drastically reduce response times for the request. To use this you
must compile Apache httpd with mod_perl and add HTML::Embperl
as the PerlHandler.
Example of Apache srm.conf or httpd.conf:
SetEnv EMBPERL_DEBUG 2285
Alias /embperl /path/to/embperl/eg
<Location /embperl/x>
SetHandler perl-script
PerlHandler HTML::Embperl
Options ExecCGI
</Location>
Another possible setup is
SetEnv EMBPERL_DEBUG 2285
<Files *.epl>
SetHandler perl-script
PerlHandler HTML::Embperl
Options ExecCGI
</files>
AddType text/html .epl
Don't forget the AddType. In this setup, all files ending with .epl are processed by Embperl.
See the section EMBPERL_DEBUG (dbgLogLink and EMBPERL_VIRTLOG) to find out how you can configure Embperl so you can view the log file with your browser!
NOTE: When mod_perl is compiled as loadable module (i.e. with USE_DSO) you must not load Embperl at server startup time!
See also: ``perldoc EmbperlObject'' to see how to setup Embperl so as to create your site out of small overwriteable objects.
Execute can be used to call Embperl from your own modules/scripts (for example from a Apache::Registry or CGI script) or from within another Embperl page (only 1.2b1 or higher) to nest multiple Embperl pages (for example to store a common header or footer in a different file).
There are two forms you can use for calling Execute. A short form which only takes a filename and optional additional parameters or a long form which takes a hash reference as its argument. This gives it the chance to vary the parameters according to the job that should be done.
(See eg/x/Excute.pl for more detailed examples)
See also: ``perldoc EmbperlObject'' to see how to setup Embperl so as to create your site out of small overwriteable objects and ``perldoc HTML::Embperl::Mail'' on how to use Embperl to send email.
Execute($filename, $p1, $p2, $pn) ;
This will cause Embperl to interpret the file with the name $filename and, if specified, pass any additional parameters in the array @param (just like @_ in a perl subroutine). The above example could also be written in the long form:
Execute ({inputfile => $filename,
param => [$p1, $p2, $pn]}) ;
The possible items for hash of the long form are:
A value of one tells Embperl to define the subrountines inside the file (if not already done) and to import them as perl subroutines into the current namespace.
See [$ sub $] metacommand and section about subroutines for more info.
If used under mod_perl, you should set the req_rec parameter to the Apache request record object provided by mod_perl.
If running as a CGI or offline, cleanup takes place immediately.
Example:
HTML::Embperl::Execute(..., param => [1, 2, 3]) ;
HTML::Embperl::Execute(..., param => \@parameters) ;
The array @param in the Embperl document is setup as an alias to the array. See eg/x/Excute.pl for a more detailed example.
NOTE: You should set the optDisableFormData if you have already read the form data from stdin while in a POST request. Otherwise Execute will hang and try to read the data a second time.
isa parameter (see below) you
are able to provide an inherence tree. Additionaly you can use the returned
hashref to store data for that obeject.
Example:
[# the file eposubs.htm defines two subs: txt1 and txt2 #]
[# first we create a new object #]
[- $subs = Execute ({'object' => 'eposubs.htm'}) -]
[# then we call methods inside the object #] txt1: [+ $subs -> txt1 +] <br>
txt2: [+ $subs -> txt2 +] <br>
Example:
[! Execute ({'isa' => '../eposubs.htm'}) !]
NOTE: You do not need to call Init in version >= 0.27. The initialization of Embperl takes place automatically when it is loaded.
# Get source from /path/to/your.html and # write output to /path/to/output'
HTML::Embperl::Execute ({ inputfile => '/path/to/your.html',
outputfile => '/path/to/output'}) ;
# Get source from scalar and write output to stdout # Don't forget to modify mtime if $src changes
$src = '<html><head><title>Page [+ $no +]</title></head>' ;
HTML::Embperl::Execute ({ inputfile => 'some name',
input => \$src,
mtime => 1 }) ;
# Get source from scalar and write output to another scalar
my $src = '<html><head><title>Page [+ $no +]</title></head>' ; my $out ;
HTML::Embperl::Execute ({ inputfile => 'another name',
input => \$src,
mtime => 1,
output => \$out }) ;
print $out ;
# Include a common header in an Embperl page, # which is stored in /path/to/head.html
[- Execute ('/path/to/head.html') -]
The runtime configuration is done by setting environment variables, either on the command line (when working offline) or in your web server's configuration file. Most HTTP servers understand:
SetEnv <var> <value>
If you are using Apache and mod_perl you can use
PerlSetEnv <var> <value>
The advantage of PerlSetEnv over SetEnv is that it can be used on a per directory/virtual host basis.
If specified, only files which match the given perl regular expression will be processed by Embperl, all other files will be handled by the standard Apache handler. This can be useful if you have Embperl documents and non Embperl documents (e.g. gifs) residing in the same directory. EMBPERL_FILESMATCH works only under mod_perl.
Example: # Only files which end with .htm will processed by Embperl PerlSetEnv EMBPERL_FILESMATCH \.htm$
If specified, only files which match the given perl regular expression will be processed by Embperl. All other files will return FORBIDDEN. This is especially useful in a CGI environment by making the server more secure.
Can contain a semicolon (also colon under Unix) separated file search path.
When a file is processed and the filename isn't an absolute path or
does not start with ./ (or .\ under windows), Embperl searches all
the specified directories for that file. Directories must end with a
slash (/), otherwise the entry is treated as a fileprefix.
A special handling is done if the filename starts with any number
of ../ i.e. refers to an upper directory. Then Embperl strips
the same number of entries at the start of the searchpath as the filename
contains ../.
Gives the name of the compartment from which to take the opcode mask. (See the chapter about (Safe-)Namespaces and opcode restrictions for more details.)
Specifies the initial value for $escmode (see below).
Gives the location of the log file. This will contain information about what Embperl is doing. The amount of information depends on the debug settings (see EMBPERL_DEBUG below). The log output is intended to show what your embedded Perl code is doing and to help debug it. The default is /tmp/embperl.log.
NOTE: When running under mod_perl you need to use PerlSetEnv for setting the logfile path, and mod_perl >= 1.07_03 if you load Embperl at server startup (with PerlScript or PerlModule).
The name of the package where your code will be executed. By default, Embperl generates a unique package name for every file. This ensures that variables and functions from one file do not conflict with those of another file. (Any package's variables will still be accessible with explicit package names.)
Gives a virtual location where you can access the Embperl logfile with a browser. This feature is disabled (default) if EMBPERL_VIRTLOG is not specified. See also EMBPERL_DEBUG and dbgLogLink for an Example on how to set it up in your srm.conf.
This bitmask specifies some options for the execution of Embperl. To specify multiple options, simply add the values together.
$errors = $req_rec -> prev -> pnotes('EMBPERL_ERRORS') ;
where $errors is a array reference. (1.3b5+)
If you are using a WYSIWYG editor which inserts unwanted HTML tags in your Perl expressions and escapes special characters automatically (e.g., `<' appears as `<' in the source), you should not set this option. Embperl will automatically convert the HTML input back to the Perl expressions as you wrote them.
=item optUncloseWarn = 4194304 (only 1.2b6 and above)
Disable the warnings about unclosed if, while, table etc. at the end of the file.
This is a bitmask which specifies what should be written to the log. To specify multiple debugflags, simply add the values together. The following values are defined:
Example:
SetEnv EMBPERL_DEBUG 10477
SetEnv EMBPERL_VIRTLOG /embperl/log
<Location /embperl/log>
SetHandler perl-script
PerlHandler HTML::Embperl
Options ExecCGI
</Location>
A good value to start is 2285 or 10477 if you want to view the
logfile with your browser. (Don't forget to set EMBPERL_VIRTLOG.) If
Embperl crashes, add 512 so the logfile is flushed after every line
is written and you can see where Embperl is when it crashes.
This directive gives you the possiblity to specify a non-standard way
of fetching input. Normally, Embperl reads its input (source) from
a file (or gets it from a scalar if you use Execute). Here, you can
give the name of a Perl function which is called instead of reading the
input from a file. The function must look like the following:
InputFunc ($r, $in, $cacheargs, additional parameters...) ;
Example:
open F, "filename" ; local $\ = undef ; $$in = <F> ; close F ;
mtime and inputfile
which are used to correcly cache the precompiled Perlcode.
Example:
$$cacheargs = -M "filename" ;
or
$$cacheargs = { mtime => -M "filename", inputfile => "filename" } ;
You can give additional parameters (which must be comma-separated) to EMBPERL_INPUT_FUNC which will then pass them as a string.
Example:
PerlSetEnv EMBPERL_INPUT_FUNC "InputFunc, foo, bar"
will call
InputFunc ($r, $in, $mtime, 'foo', 'bar') ;
to get the input.
EXAMPLE for an input function which does just the same as Embperl
sub Input
{
my ($r, $in, $mtime) = @_ ;
open F, $r -> filename or return NOT_FOUND ;
local $\ = undef ;
$$in = <F> ;
close F ;
$$mtime = -M $r -> filename ;
return 0 ;
}
See also ProxyInput below, for an input function which comes with Embperl.
NOTE: There are also two modules (HTML::EmbperlChain and Apache::EmbperlFilter) which allow you to chain Embperl and other modules together.
This directive allows you to specify a non-standard way
of dealing with output. Normally, Embperl sends its output (source) to
a file/the browser (or to a scalar if you use Execute). Here, you can
give the name of a Perl function which is called instead of sending the
output to a file/the browser. The function must look like the following:
OutputFunc ($r, $out, additional parameters...) ;
You can give additional parameters (which must be comma-separated) to EMBPERL_OUTPUT_FUNC, which will then pass them as a string.
Example:
PerlSetEnv EMBPERL_OUTPUT_FUNC "OutputFunc, foo, bar"
will call
OutputFunc ($r, $out, 'foo', 'bar') ;
for output.
EXAMPLE for an ouput function which does just the same as Embperl
sub Output
{
my ($r, $out) = @_ ;
$r -> send_http_header ;
$r -> print ($$out) ;
return 0 ;
}
See also LogOutput below, for an output function which comes with Embperl.
NOTE: There are also two modules (HTML::EmbperlChain and Apache::EmbperlFilter) which allow you to chain Embperl and other modules together.
Specifies which host the MailFormTo function uses as SMTP server. Default is localhost.
(only 1.3b4 or above) Specifies which host/domain the MailFormTo function uses in the HELO/EHLO command. A reasonable default is normaly choosen by Net::SMTP, but depending on your installation it may neccessary to set it manualy.
(only 1.2.1 or above) Specifies which the email address that is used as sender by MailFormTo. Default is www-server@server_name.
(only 1.2.1 or above) Debugsetting for Net::SMTP. Default is 0.
If set all errors will be send to the email adress given.
(only 1.2b4 or above) Set the name that Embperl uses when it sends the cookie with the session id. Default is EMBPERL_UID.
(only 1.2b4 or above) Set the domain that Embperl uses for the cookie with the session id. Default is none.
(only 1.2b4 or above) Set the path that Embperl uses for the cookie with the session id. Default is none.
(only 1.2b4 or above) Set the expiration date that Embperl uses for the cookie with the session id. You can specify the full date or relativ values (1.3b5 or higher). Examples: +30s +10m +1h -1d +3M +10y Default is none.
Space separated list of object store and lock manager (and optionally the serialization and id generating class) for Apache::Session (see Session handling)
List of arguments for Apache::Session classes (see Session handling) Arguments that contains spaces can be quoted. Example:
PerlSetEnv EMBPERL_SESSION_ARGS "DataSource=dbi:mysql:session UserName=www 'Password=secret word'"
Set the class that performs the Embperl session handling. Default until
1.3.3 was HTML::Embperl::Session, starting with 1.3.4 it is
Apache::SessionX. To get the old session behaviour set it to
HTML::Embperl::Session. You can overwrite HTML::Embperl::Session and
specify the name of your class within this variable. This gives you
the possibility to implement your own session handling.
Embperl understands two categories of commands. The first one are special Embperl commands, and the second category consists of some HTML tags which can trigger special processing. Embperl commands can span multiple lines and need not start or end at a line boundary.
Before the special Embperl commands are processed, and for the VALUE attribute of the INPUT tag (see below), all HTML tags are removed and special HTML characters are translated to their ASCII values (e.g., `<' is translated to `<'). You can avoid this behavior by preceding the special character or HTML tag with a backslash. This is done in case your favorite (WYSIWYG) HTML editor inserts tags like line breaks or formatting into your Embperl commands where you don't want them.
VERY IMPORTANT NOTE: If you do use an ASCII editor to write your HTML documents, you should set the option optRawInput so that Embperl does not preprocess your source. You can also HTML-escape your code (i.e. write `<' instead of `<'), to avoid ambiguity. In most cases it will also work without the optRawInput and HTML-escaping, but in some cases Embperl will detect an HTML tag were there isn't one.
If you have any trouble with your code, especially with HTML tags or filehandles in your Perl code, be sure to understand input- and output- escaping and unescaping. Read the section ``Inside Embperl'' to see what's going on!!
All Embperl commands start with a `[' and end with a `]'. To get a real `[' you must enter `[['.
Embperl does not use SGML comments (i.e., <! ... !> or similar things) because some HTML editors can't create them, or it's much more complicated. Since every HTML editor takes (or should take) `[' and `]' as normal text, there should be no problem.
Replace the command with the result you get from evaluating the Perl code. The Perl code can be anything which can be used as an argument to a Perl eval statement. (See (Safe-)Namespaces and opcode restrictions below for restrictions.) Examples:
[+ $a +] Replaces the [+ $a +] with the content of
the variable $a
[+ $a+1 +] (Any expression can be used)
[+ $x[$i] +] (Arrays, hashes, and more complex
expressions work)
NOTE: Whitespace is ignored. The output will be automatically
HTML-escaped (e.g., `<' is translated to `<') depending on the
value of the variables $escmode. You do not have to worry about
it.
Executes the Perl code, but deletes the whole command from the HTML output.
Examples:
[- $a=1 -] Set the variable $a to one.
No output will be generated.
[- use SomeModule ; -] You can use other modules. NOTE the semicolon!
[- $i=0; while ($i<5) {$i++} -] Even more complex
statements or multiple
statements are possible.
NOTE: Statements like if, while, for, etc., must be contained in a
single Embperl command. You cannot have the if in one command block
and the terminating `}' or else in another.
NOTE: To define subroutines, use [! Perl Code !] (see below) instead of
[- ... -] to avoid recompilation of the subroutine on every request.
Same as [- Perl Code -] with the exception that the code is only executed at the first request. This could be used to define subroutines, or do one-time initialization.
(only version 1.2b2 or higher) EXPERIMENTAL!
This is similar to [- Perl Code -]. The main difference is, while [- Perl Code -] always has its own scope, all [* Perl code *] blocks runs in the same scope. This allows you to define ``local'' variables with a scope of the whole page. Normally, you don't need to use local, because Embperl takes care of separate namespaces of different documents and cleanup after the request is finished, but in special cases it's necessary. For example, if you want to recursively call an Embperl document via Execute.
There is a second reason to use the [* Perl code *] instead of the [- Perl Code -]. If you like to use perl's control structures. Perl's if, while, for etc. can not span mulitple [- Perl Code -] blocks, but it can span multiple [* Perl Code *].
Example:
[* foreach $i (1..10) { *]
[- $a = $i + 5 -]
loop count + 5 = [+ $a +] <br>
[* } *]
The following B<won't> work:
[- foreach $i (1..10) { -]
some text here <br>
[- } -]
The same can be done with Embperl meta commands (see below)
[$ foreach $i (1..10) $]
[- $a = $i + 5 -]
loop count + 5 = [+ $a +] <br>
[$ endforeach $]
NOTE 1: [* ... *] blocks _must_ always end with a ;,{ or }
NOTE 2: [* ... *] cannot apear inside a html tag that is interpreted by Embperl (unless you disable the interpretation of such tags like table, input etc.)
NOTE 3: There are still benefits of using [- ... -] and metacommands: - much better debugging in the log file. - no restriction on where they can be used. You can use them anywhere; even inside html tags that are interpreted by Embperl.
(only version 1.2b2 or higher)
This is a comment block. Everything between the [# and the #] will be removed from the output.
NOTE 1: The [* ... *] blocks are interpreted before the comment block, so they are executed also inside a comment.
NOTE 2: Everything (except [* ... *]) is really removed from the source, so you can also use the [# ... #] block to take a part out of your document.
Execute an Embperl metacommand. Cmd can be one of the following. (Arg varies depending on <Cmd>).
Example:
[$ if $ENV{REQUEST_METHOD} eq 'GET' $]
Method was GET<BR>
[$ else $]
Method other than GET used<BR>
[$ endif $]
This will send one of the two sentences to the client, depending on the request method used to retrieve the document.
Example: (see eg/x/loop.htm)
[- $i = 0; @k = keys %ENV -]
[$ while ($i < $#k) $]
[+ $k[$i] +] = [+ $ENV{$k[$i]} +]<BR>
[- $i++ -]
[$ endwhile $]
This will send a list of all environment variables to the client.
NOTE: The `<' is translated to `<' before calling Perl eval, unless optRawInput is set.
Example:
[- $i = 0 -]
[$ do $]
[+ $i++ +] <BR>
[$ until $i > 10 $]
Example:
[- @arr = (1, 3, 5) -]
[$ foreach $v @arr $]
[+ $v +] <BR>
[$ endforeach $]
%fdat, %idat is used for the second.
If the third parameter is specified, the fields are written in the order they appear in this array. That is, all keys of the first hash must be properly sorted in this array. This is intended for situations where you want to pass data from one form to the next, for example, two forms which should be filled in one after the other. (Examples might be an input form and a second form to review and accept the input, or a Windows-style ``wizard''). Here you can pass along data from previous forms in hidden fields. (See eg/x/neu.htm for an example.) If you use just the 'hidden' command without parameters, it simply generates hidden fields for all form fields submitted to this document which aren't already contained in another input field.
Example:
<FORM ACTION="inhalt.htm" METHOD="GET">
<INPUT TYPE="TEXT" NAME="field1">
[$ hidden $]
</FORM>
If you request this with
http://host/doc.htm?field1=A&;field2=B&field3=C
the output will be
<FORM ACTION="inhalt.htm" METHOD="GET">
<INPUT TYPE="TEXT" NAME="feld1" VALUE="A">
<INPUT TYPE="HIDDEN" NAME="field2" VALUE="B">
<INPUT TYPE="HIDDEN" NAME="field3" VALUE="C">
</FORM>
NOTE: This should only be used for a small amount of data, since the
hidden fields are sent to the browser, which sends it back with the
next request. If you have a large amount of data, store it in a file
with a unique name and send only the filename in a hidden field. Be
aware of the fact that the data can be changed by the browser if the
user doesn't behave exactly as you expect. Users have a nasty habit of
doing this all of the time. Your program should be able to handle
such situations properly.
Example:
[$var $a %b @c $]
This is the same as writing the following in normal Perl code:
use strict ;
use vars qw($a %b @c) ;
NOTE 1: `use strict' within an Embperl document will only apply to the block in which it occurs.
Defines a Embperl subroutine. Example:
[$ sub foo $]
<p> Here we do something </p>
[$ endsub $]
You can call this subroutine either as a normal Perl subroutine
[- foo -]
or via the HTML::Embperl::Execute function.
[- Execute ('#foo') # short form -]
[- Execute ({ sub => 'foo'}) # long form -]
The difference is that the Execute function will reset the internal states of Embperl like they were before the subrountine call, when the subroutine returns. Also Execute could handle recursive call, which currently not work when calling it as a Perl subroutine.
You may also pass Parameters to the subroutine:
[$ sub foo $]
[- $p = shift -]
<p> Here we show the first parameter [+ $p +]</p>
[$ endsub $]
[- foo ('value') -]
If you have a couple of commonly used subroutines you can define then in one file and import them into the modules where they are neccesary:
[- Execute ({ inputfile => 'mylib.htm', import => 1 }) -]
This will import all subroutines from the file mylib.htm into the current page where they could call just as a normal Perl subroutine.
Embperl recognizes the following HTML tags in a special way. All others are simply passed through, as long as they are not part of a Embperl command.
Embperl generates as many rows or columns as necessary. This is done by using the magic variables $row, $col, and $cnt. If you don't use $row/$col/$cnt within a table, Embperl does nothing and simply passes the table through.
Embperl checks if any of $row, $col, or $cnt is used. Embperl repeats all text between <table> and </table>, as long as the expressions in which $row or $cnt occurs are defined.
Embperl repeats all text between <tr> and </tr>, as long as the expressions in which $col or $cnt occurs are defined.
See also $tabmode (below) for end-of-table criteria.
Examples: (see eg/x/table.htm for more examples)
[- @k = keys %ENV -]
<TABLE>
<TR>
<TD>[+ $i=$row +]</TD>
<TD>[+ $k[$row] +]</TD>
<TD>[+ $ENV{$k[$i]} +]</TD>
</TR>
</TABLE>
This will show all entries in array @k (which contains the keys from %ENV), so the whole environment is displayed (as in the while example), with the first column containing the zero-based index, the second containing the content of the variable name, and the third the environment variable's value.
This could be used to display the result of a database query if you have the result in an array. You may provide as many columns as you need. It is also possible to call a 'fetch' subroutine in each table row.
Example:
<FORM METHOD=``POST''> <P>Select Tag</P>
If you request this document with list.htm?SEL1=x you can specify that the element which has a value of x is initially selected
<P><SELECT NAME="SEL1">
<OPTION VALUE="[+ $v[$row] +]">
[+ $k[$row] +]
</OPTION>
</SELECT></P>
</FORM>
%idat and %fdat. If the
input tag has no value and a key exists with the same text as the
NAME attribute of the input tag, Embperl will generate a VALUE
attribute with the corresponding value of the hash key.
All values of <INPUT> tags are stored in the hash %idat, with NAME
as the hash key and VALUE as the hash value. Special processing is
done for TYPE=RADIO and TYPE=CHECKBOX. If the VALUE attribute
contains the same text as the value of the hash the CHECKED attribute
is inserted, else it is removed.
So, if you specify, as the ACTION URL, the file which contains the form itself, the form will be redisplayed with same values as entered the first time. (See eg/x/neu.htm for an example.)
TEXTAREA tag is treated exactly like other input fields.
This can also be used to set http headers. When running under mod_perl http-headers can also be set by the function header_out
Example of how to set a http header:
<META HTTP-EQUIV="Language" CONTENT="DE">
This is the same as using the Apache function
[- $req_rec -> header_out("Language" => "DE"); -]
HREF attribute of the A Tags and the
SRC attribute of the other Tags are URL escaped instead of HTML escaped.
(see also the $escmode manpage). Also, when inside such a URL, Embperl expands array and hash references
to URL parameter syntax. Example:
[-
$A = { A => 1, B => 2 } ; # Hashreference
@A = (X, 9, Y, 8, Z, 7)
-]
<A HREF="http://localhost/tests?[+ $A +]"> <A HREF="http://localhost/tests?[+ \@A +]">
is expanded by Embperl to
<A HREF="http://localhost/tests?A=1&;amp;B=2"> <A HREF="http://localhost/tests?X=9&;amp;Y=8&Z=7">
The scope of a variable declared with my or local ends at the end of the enclosing [+/- ... -/+] block; the [+/- ... -/+] blocks act much like Perl's { ... } in that regard.
Global variables (everything not declared with my or local) will be undef'ed at the end of each request, so you don't need to worry about any old variables laying around and causing suspicious results. This is only done for variables in the package the code is eval'ed in -- every variable that does not have an explicit package name. All variables with an explicit package name (i.e., in modules you use) will stay valid until the httpd child process dies. Embperl will change the current package to a unique name for every document, so the influence between different documents is kept to a minimum. You can set the name of the package with EMBPERL_PACKAGE. (See also (Safe-)Namespaces and opcode restrictions.)
Since a CGI script is always a process of its own, you don't need to worry about that when you use Embperl as a CGI script.
If you need to declare variables which need to live longer than just one
HTTP request (for example, a database handle), you must either put it's
name in the hash %CLEANUP or declare them in
another package (i.e., $Persistent::handle instead of $handle).
If you want to use the strict pragma, you can do this by using the var metacommand to declare your variables.
NOTE: Bacause Apache::DBI has its own namespace, this module will
work together with Embperl to maintain your persistent database
connection.
You can disable the automatic cleanup of global variables with EMBPERL_OPTIONS or the cleanup parameter of the Execute function.
You can define exceptions to the cleanup rule with the hash %CLEANUP.
If you like to do your own cleanup you can define a subroutine CLEANUP in your document. This will be called right before the variables are cleaned up, but after the connection to the client is closed.
EXAMPLE:
[! sub CLEANUP { close FH ; } !]
Embperl has some special variables which have a predefined meaning.
Contains the environment as seen from a CGI script.
Contains all the form data sent to the script by the calling form. The NAME attribute builds the key and the VALUE attribute is used as the hash value. Embperl doesn't care if it is called with the GET or POST method, but there may be restrictions on the length of parameters using GET -- not from Embperl, but perhaps from the web server, especially if you're using Embperl's CGI mode -- it is safer to use POST.
If multiple fields with the same name are sent to a Embperl page, they will put in the same hash element and separated be tabs. You can split it up in an array, by writting:
@array = split (/\t/, $fdat{'fieldname'}) ;
Embperl also supports ENCTYPE multipart/form-data, which is used for file uploads. The entry in %fdat corresponding to the file field will be a filehandle, as with CGI.pm. (Embperl uses CGI.pm internally to process forms encoded with multipart/form-data.)
File upload example:
HTML page:
<FORM METHOD="POST" ENCTYPE="multipart/form-data">
<INPUT TYPE="FILE" NAME="ImageName">
</FORM>
Embperl ACTION:
[- if (defined $fdat{ImageName}) {
open FILE, "> /tmp/file.$$";
print FILE $buffer
while read($fdat{ImageName}, $buffer, 32768);
close FILE;
}
-]
When you have installed CGI.pm 2.46 or above, you may also retrieve the filename (local filename, as it was on the browser side) and the information provided by the CGI.pm uploadInfo function. To get the filename, simply print out the value of the corresponding %fdat entry, instead of using it as a filehandle. To get the uploadInfo use the fieldname with a dash in front of it:
Example:
# ImageName is the NAME of the field, you must replace it with whatever
# name is given in your HTML code
Filename: [+ $fdat{ImageName} +] <br>
Content-Type: [+ $fdat{-ImageName} -> {'Content-Type'} +] <br>
NOTE: The way uploadInfos are accessed before 1.2b11 is not supported anymore.
NOTE: This works the other
way as well: any input fields with names that are
%fdat keys, and without values, will have their values automatically set to
the appropriate %fdat value. See HTML Tags INPUT/OPTION/TEXTAREA.
Contains all the field names in the order in which they were sent by the browser. This is normally -- but not necessarily -- the order in which they appear in your form.
Contains all the values from all input tags processed so far.
You can use %udat to store per user data. As long as you don't use %udat, nothing happens, but as soon as you write anything to %udat, Embperl creates a session id and sends it via a cookie to the browser. The data you have written to %udat is stored by Apache::Session. The next time the same user request an Embperl page, the browser sends the cookie with the session id back and Embperl fills the %udat hash from Apache::Session with the same values as you have stored for that user. (See also Session handling)
You can use %mdat to store per module/page data. As long as you don't use %mdat, nothing happens, but as soon as you write anything to %mdat, Embperl creates a session id and stores the data via Apache::Session. The next time any user hits the same Embperl page, Embperl fill the %mdat hash from Apache::Session with the same values as you have stored within the last request to that page. (See also Session handling)
Row and column counts for use in dynamic tables. (See ``HTML tag table''.)
Maximum number of rows or columns to display in a table. To prevent endless loops, $maxrow defaults to 100 and $maxcol to 10. (See ``HTML tag table''.)
Contains the number of table cells displayed so far. (See ``HTML tag table''.)
Determines how the end of a dynamic table is detected. Tables are always limited to the size specified in $maxrow and $maxcol, but can be ended early when the row ($row) and column ($col) variables become undefined. $tabmode operates as follows:
end of row
The default is 17, which is correct for all sort of arrays. You should rarely need to change it. The two values can be added together.
Turn HTML and URL escaping on and off. The default is on ($escmode = 3).
NOTE: Normaly you can disable escaping by preceeding the item that normaly is escaped with a backslash. While this is a handy thing, it could be very dangerous in situations, where content that is inserted by some user is redisplayed, because they can enter arbitary HTML and preceed them with a backslash to avoid correct escaping when their input is redisplayed again. To avoid this problem, add 4 to the values below. This will cause Embperl to ignore the backslash when it does output escaping at all. (only 1.3b4 and above)
NOTE 2: If you want to output binary data, you must set the escmode to zero. (only 1.3b6 and above)
A, EMBED, IMG, IFRAME, FRAME and LAYER tags.
This variable is only available when running under control of mod_perl. It contains the request record needed to access the Apache server API. See perldoc Apache for more information.
This is the filehandle of the Embperl logfile. By writing `print LOG ``something''' you can add lines to the logfile. NOTE: The logfile line should always start with the pid of the current process and continue with a four-character signature delimited by a ':', which specifies the log reason.
Example: print LOG ``[$$]ABCD: your text\n'' ;
If you are writing a module for use under Embperl you can say
tie *LOG, 'HTML::Embperl::Log';
to get a handle by which you can write to the Embperl logfile.
This filehandle is tied to Embperl's output stream. Printing to it has the same effect as using the [+ ... +] block. (See also optRedirectStdout)
Will be setup by the 'param' parameter of the Execute function. Could be used to pass parameters to an Embperl document and back. (see Execute for further docs)
You can put any http headers you want to send into this hash. If you set a location header, Embperl will automaticly set the status to 301 (Redirect). Example:
[- $http_headers_out{'Location'} = "http://www.ecos.de/embperl/"; -]
Starting with version 1.3.2 all headers with the exception ``Location'' and ``Content-Type'' can take multiple values. For instance, if you wanted to set two cookies, you can proceed as follows:
[- $http_headers_out{'Set-Cookie'} =
['name=cook1;value=2;','name=cook2;value=b'] ; -]
If you supply multiple values for ``Location'' or ``Content-Type'' via an array reference, then Embperl will simply use the first in the list. Empty arrays will be ignored. For instance, the following will neither change the status to 301 nor create a Location: line in the HTTP headers:
[- $http_headers_out{'Location'} = [] ; -]
see also META HTTP-EQUIV=
All options (see EMBPERL_OPTIONS) and all debugging flags (see EMBPERL_DEBUG) can be read and set by the corresponding variables.
Example:
[- $optRawInput = 1 -] # Turn the RawInput option on
Now write something here
[- $optRawInput = 0 -] # Turn the RawInput option off again
[+ $dbgCmd +] # Output the state of the dbgCmd flag
There are a few exceptions, where the variables can only be read. Setting of such options must be done via the config-files. Read-only variables are:
Embperl cleanups up only variables with are defined within the Embperl page. If you want Embperl to cleanup additional variables you can add them to the hash %CLEANUP, with the key set to the variable name and the value set to one. The other way you could prevent Embperl from cleaning up some variables, is by adding them to this hash, with values of zero.
Same purpose as %CLEANUP, but you may add filenames. All variables defined inside that file
will be cleaned up.
From 1.2b1 and higher Embperl is able to handle per user sessions for you. You can store any data in the %udat hash and if the same user requests an Embperl document again, you will see the same values in that hash again.
From 1.2b2 and higher Embperl is able to handle per module/page persistent data for you. You can store any data in the %mdat hash and if any request comes to the same Embperl document, you will see the same values in that hash again.
Session handling has changed from 1.3.3 to 1.3.4 and 2.0b3 to 2.0b4. You must either install Apache::SessionX or set
PerlSetEnv EMBPERL_SESSION_HANDLER_CLASS "HTML::Embperl::Session"
to get the old behaviour. If you have Apache::SessionX installed, you don't have to make addtional configuration, otherwise you must do the following things. You are also able to override the Apache::SessionX defaults, by using the following parameters:
To configure Embperl to do session management for you, you must
have installed Apache::Session (1.53 or higher) and tell Embperl which
storage and locker classes you would like to use for
Apache::Session. This is done by setting the environment variable
EMBPERL_SESSION_CLASSES.
If you want to use a MySQL database for storing your sessions, you may have a
startup.pl for your httpd which looks like this:
BEGIN
{
$ENV{EMBPERL_SESSION_CLASSES} = "MySQL Semaphore" ;
$ENV{EMBPERL_SESSION_ARGS} = "DataSource=dbi:mysql:session UserName=test" ;
} ;
use HTML::Embperl ;
or you may put this in the httpd/srm.conf:
PerlSetEnv EMBPERL_SESSION_CLASSES "MySQL Semaphore" PerlSetEnv EMBPERL_SESSION_ARGS "DataSource=dbi:mysql:session UserName=test" PerlModule HTML::Embperl ;
Refer to the Apache::Session docs (e.g. Apache::Session::Store::MySQL) on how to setup your database tables.
EMBPERL_SESSION_ARGS is a space separated list of name/value pairs, which gives
additional arguments for Apache::Session classes.
Here is an example for using a filesystem based storage:
PerlSetEnv EMBPERL_SESSION_CLASSES ``File Semaphore'' PerlSetEnv EMBPERL_SESSION_ARGS ``Directory=/path/to/your/sessions''
Refer to the Apache::Session docs to find out which other storage/locker methods are available.
EMBPERL_SESSION_CLASSES can (optionally) take two more classnames, which specify
the class for serialization (Default: Storable) and for generating the id
(Default: MD5).
NOTE: The above configuration works only with Apache::Session 1.52 and Embperl 1.3b5
or above. Older versions of Embperl only support Apache::Session 1.0x, which has
different parameters for EMBPERL_SESSION_CLASSES
(e.g. $ENV{EMBPERL_SESSION_CLASSES} = "DBIStore SysVSemaphoreLocker" ; )
Apache::Session 1.0x still works with this Embperl version.
Now you are able to use the %udat and %mdat hashes for your user/module sessions. As long as you don't touch %udat or %mdat, Embperl will not create any session, and Apache::Session is not loaded. As soon as you store any value to %udat, Embperl will create a new session and send a cookie to the browser to maintain its id, while the data is stored by Apache::Session. (Further version may also be able to use URL rewriting for storing the id). When you modify %mdat, Embperl will store the data via Apache::Session and retrieve it when the next request comes to the same page.
This can be used from a script that will later call HTML::Embperl::Execute to preset the session so it's available to the calling script.
undef otherwise.
$Inputfile, %mdat is not setup.
Returns a reference to %udat or, if call in an array context, a reference to %udat
and %mdat. See also CleanupSession.
Returns a reference to %udat or, if called in an array context, a reference to %udat
and %mdat. This could be used by modules that are called from inside an Embperl page,
where the session management is already setup. If called as a method $r must be
a HTML::Embperl::Req object, which is passed as first parameter to every Embperl page in @_ .
Must be called at the end of a script by scripts that use SetupSession,
but do not call HTML::Embperl::Execute.
If called as a method $r must be
a HTML::Embperl::Req object, which is passed as first parameter to every Embperl page in @_ .
Deletes the session data and removes the cookie from the browser.
If called as a method $r must be
a HTML::Embperl::Req object, which is passed as first parameter to every Embperl page in @_ .
Triggers a resend of the cookie. Normaly the cookie is only send the first time.
If called as a method $r must be
a HTML::Embperl::Req object, which is passed as first parameter to every Embperl page in @_ .
Must be called by scripts that use SetupSession,
but do not call HTML::Embperl::Execute. This is neccessary to set the cookie
for the session id, in case a new session is created, which is normaly done by
HTML::Embperl::Execute. If called as a method $r must be
a HTML::Embperl::Req object, which is passed as first parameter to every Embperl page in @_ .
Since most web servers will contain more than one document, it is necessary to protect the documents against each other. Embperl does this by using Perl namespaces. By default, Embperl executes every document in its own namespace (package). This will prevent documents from accidentally overriding the other's data. You can change this behavior (or simply the package name) with the configuration directive EMBPERL_PACKAGE. NOTE: By explicitly specifying a package name, you can access data that is used by another document.
If Embperl is used by more than one person, it may be neccessary to protect documents from each other. To do this, Embperl gives you the option of using safe namespaces. Each document runs in its own package and can't access anything outside of this package. (See the documentation of Safe.pm for a more detailed discussion of safe namespaces.)
To make a document run in a safe namespace, simply add optSafeNamespace to EMBPERL_OPTIONS. The default package name used is the same as in normal operation and can be changed with EMBPERL_PACKAGE. NOTE: From the perspective of the document being executed, the code is running in the package main!
A second option to make Embperl more secure is the use of the opcode restriction mask. Before you can use the opcode mask, you must set up a safe compartment.
B<$cp = HTML::Embperl::AddCompartment($name);>
This will create a new compartment with a default opcode mask and the name $name. (The name is used later to tell Embperl which compartment to use.) Now you can change the operator mask. For example:
B<$cp->deny(':base_loop');>
In your configuration you must set the option optOpcodeMask in EMBPERL_OPTIONS and specify from which compartment the opcode mask should be taken by setting EMBPERL_COMPARTMENT.
Example (for use with mod_perl):
B<srm.conf:>
PerlScript startup.pl
SetEnv EMBPERL_DEBUG 2285
Alias /embperl /path/to/embperl/eg
<Location /embperl/x>
SetHandler perl-script
PerlHandler HTML::Embperl
Options ExecCGI
PerlSetEnv EMBPERL_OPTIONS 12
PerlSetEnv EMBPERL_COMPARTMENT test
</Location>
B<startup.pl:>
$cp = HTML::Embperl::AddCompartment('test');
$cp->deny(':base_loop');
This will execute the file startup.pl on server startup. startup.pl sets up a compartment named `test', which will have a default opcode mask and additionaly, will have loops disabled. Code will be executed in a safe namespace.
NOTE: The package name from the compartment is NOT used!
Look at the documentation of Safe.pm and Opcode.pm for more detailed information on how to set opcode masks.
AddCompartment($Name)Adds a compartment for use with Embperl. Embperl only uses the opcode mask from it, not the package name. AddCompartment returns the newly- created compartment so you can allow or deny certain opcodes. See the Safe.pm documentation for details of setting up a compartment. See the chapter about (Safe-)Namespaces and opcode restrictions for details on how Embperl uses compartments.
Example:
$cp = HTML::Embperl::AddCompartment('TEST');
$cp->deny(':base_loop');
Sends the content of the hash %fdat in the order specified by @ffld to the given $MailTo addressee, with a subject of $Subject. If you specify $ReturnField the value of that formfield will be used as Return-Path. Usually, this will be the field where the user enters his e-mail address in the form.
If you specifiy the following example code as the action in your form
<FORM ACTION="x/feedback.htm" METHOD="POST"
ENCTYPE="application/x-www-form-urlencoded">
The content of the form will be mailed to the given e-mail address.
MailFormTo uses EMBPERL_MAILHOST as SMTP server or localhost if non given.
Example:
<HTML>
<HEAD>
<TITLE>Feedback</TITLE>
</HEAD>
<BODY>
[- MailFormTo('webmaster@domain.xy',
'Mail from WWW Form', 'email') -]
Your data has been successfully sent!
</BODY>
</HTML>
This will send an email with all the form fields to webmaster@domain.xy, with the Subject 'Mail from WWW Form' and will set the Return-Path of the mail to the address which was entered in the field with the name 'email'.
NOTE: You must have Net::SMTP (from the libnet package) installed to use this function.
exit will override the normal Perl exit in every Embperl document. Calling exit will immediately stop any further processing of that file and send the already-done work to the output/browser.
NOTE 1: If you are inside of an Execute, Embperl will only exit this Execute, but the file which called the file containing the exit with Execute will continue.
B<NOTE 2:> If you write a module which should work with Embperl under mod_perl, you must use Apache::exit instead of the normal Perl exit (as always when running under mod_perl).
B<USAGE in srm.conf:>
<Location /embperl/ifunc> SetHandler perl-script PerlHandler HTML::Embperl Options ExecCGI PerlSetEnv EMBPERL_INPUT_FUNC "ProxyInput, /embperl/ifunc, http://otherhost/otherpath"; </Location>
This input function will request the source from another URL instead of reading it from the disk. In the above USAGE Example, a request to /embperl/ifunc/foo.html, will first fetch the URL http://otherhost/otherpath/foo.html, and then it will process this document by Embperl and then it will send it to the browser.
This could be used to process documents by mod_include and Embperl, so in one document there can be both Server-Side Includes and Embperl Commands.
Example B<srm.conf> for B<SSI> and B<Embperl>:
<Location /embperl> SetHandler perl-script PerlHandler HTML::Embperl Options ExecCGI PerlSetEnv EMBPERL_INPUT_FUNC "ProxyInput, /embperl, http://localhost/src"; </Location>
<Location /src> SetHandler server-parsed Options +Includes </Location>
The source files must be in the location /src, but they will be requested via the URI /embperl. Every request to /embperl/foo.html will do a proxy-request to /src/foo.html. The file /src/foo.html will be processed by mod_include and then sent to Embperl, where it can be processed by Embperl before being sent to the browser. It would also be possible to use two httpd's on different ports. In this configuration, the source and the URI location could be the same.
B<USAGE in srm.conf:>
<Location /embperl/ofunc> SetHandler perl-script PerlHandler HTML::Embperl Options ExecCGI PerlSetEnv EMBPERL_OUTPUT_FUNC "LogOutput, /usr/msrc/embperl/test/tmp/log.out" </Location>
LogOutput is a custom output function. It sends the output to the browser and writes the output to a unique file. The filename has the form ``$basepath.$$.$LogOutputFileno''.
If Embperl encounters a piece of Perl code ([+/-/!/$ .... $/!/-/+]) it takes the following steps.
Steps 1-4 take place only the first time the Perl code is encountered. Embperl stores the eval'ed subroutine, so all subsequent requests only need to execute steps 5-7.
Steps 6 and 7 take place only for code surrounded by [+ ... +].
What does this mean?
Let's take a piece of code like the following:
[+ <BR> $a = "This '>' is a greater-than sign" <BR> +]
[+ $a = "This '>' is a greater-than sign" +]
The <BR>s were inserted by some WYSIWYG HTML editor (e.g., by hitting return to make the source more readable. Also, such editors often generate ``random'' tags like <FONT>, etc.). Embperl removes them so they don't cause syntax errors.
There are cases where you actually want the HTML tag to be there. For example, suppose you want to output something like
[+ "<FONT COLOR=$col>" +]
If you write it this way, Embperl will just remove everything, leaving only
[+ "" +]
There are several ways to handle this correctly.
a. <FONT COLOR=[+$col+]>
Move the HTML tag out of the Perl code. This is the best way, but
it is not possible every time.
b. [+ "\<FONT COLOR=$col>" +]
You can escape the opening angle bracket of the tag with `\'.
c. [+ "<FONT COLOR=$col>" +]
You can use the HTML escapes instead of the ASCII characters.
Most HTML editors will automatically do this. (In this case,
you don't have to worry about it at all.)
d. Set optRawInput (see below).
This will completely disable the removal of HTML tags.
NOTE: In cases b-d, you must also be aware of output escaping (see below).
You should also be aware that Embperl will interpret the Perl spaceship operator (<>) as an HTML tag and will remove it. So instead of
[- $line = <STDIN>; -]
you need to write either
a. [- $line = \<STDIN>; -] b. [- $line = <STDIN>; -]
Again, if you use a high-level HTML editor, it will probably write version (b) for you automatically.
Since Perl doesn't understand things like $a < $b, Embperl will translate it to $a < $b. If we take the example from earlier, it will now look like
[+ $a = "This '>' is a greater sign" +]
This step is done to make it easy to write Perl code in a high-level HTML editor. You do not have to worry that your editor is writing > instead of > in the source.
Again, sometimes you need to have such escapes in your code. You can write them
a. \>
Escape them with a `\' and Embperl will not translate them.
b. &gt;
Write the first `&' as its HTML escape (&). A normal HTML
editor will do this on its own if you enter > as text.
c. Set optRawInput (see below)
This will completely disable the input translation.
Since not all people like writing in a high level or WYSIWYG HTML editor, there is an option to disable steps 1 and 2. You can use the optRawInput in EMBPERL_OPTIONS to tell Embperl to leave the Perl code as it is. It is highly recommended to set this option if you are writing your HTML in an ASCII editor. You normally don't want to set it if you use some sort of high level HTML editor.
You can also set the optRawInput in your document by using $optRawInput, but you must be aware that it does not have any consequences for the current block, because the current block is translated before it is executed. So write it in separate blocks:
[- $optRawInput = 1 -] [- $line = <FILEHANDLE> -]
All carriage returns (\r) are removed from the Perl code, so you can write source on a DOS/Windows platform and execute it on a UNIX server. (Perl doesn't like getting carriage returns in the code it parses.)
The next step generates a subroutine out of your Perl code. In the above example it looks like:
sub foo { $a = ``This '>' is a greater sign'' }
The subroutine is now stored in the Perl interpreter in its internal precompiled format and can be called later as often as necessary without doing steps 1-4 again. Embperl recognizes if you request the same document a second time and will just call the compiled subroutine. This will also speed up the execution of dynamic tables and loops, because the code inside must be compiled only on the first iteration.
Now the subroutine can be called to actually execute the code.
If Embperl isn't executing a [+ ... +] block we are done. If it is a [+ ... +] block, Embperl needs to generate output, so it continues.
Our example returns the string:
``This '>' is a greater sign''
The greater sign is literal text (and not a closing html tag), so according to the HTML specification it must be sent as > to the browser. In most cases, this won't be a problem, because the browser will display the correct text if we send a literal '>'. Also we could have directly written > in our Perl string. But when the string is, for example, the result of a database query and/or includes characters from national character sets, it's absolutely necessary to send them correctly-escaped to the browser to get the desired result.
A special case is the <A> HTML tag. Since it includes a URL, the text must be URL-escaped instead of HTML-escaped. This means special characters like `&' must be sent by their hexadecimal ASCII code and blanks must be translated to a `+' sign. If you do not do this, your browser may not be able to interpret the URL correctly.
Example:
<A HREF="http://host/script?name=[+$n+]">
When $n is ``My name'', the requested URL, when you click on the hyperlink, will be
http://host/script?name=My+name
In some cases it is useful to disable escaping. This can be done by the variable $escmode.
Example: (For better readability, we assume that optRawInput is set. Without it, you need to cover the Embperl pre-processing described in steps 1-3.)
[+ "<FONT COLOR=5>" +]
This will be sent to the browser as <FONT COLOR=5>, so you
will see the tag on the browser screen instead of the browser
switching the color.
[+ local $escmode=0 ; "<FONT COLOR=5>" +]
This will (locally) turn off escaping and send the text as a plain
HTML tag to the browser, so the color of the output will change.
NOTE: You cannot set $escmode more than once inside a [+ ... +] block.
Embperl uses the first setting of $escmode it encounters inside the block.
If you need to change $escmode more than once, you must use multiple
[+ ... +] blocks.
Now everything is done and the output can be sent to the browser. If you haven't set dbgEarlyHttpHeaders, the output is buffered until the successful completion of document execution, and is sent to the browser along with the HTTP headers. If an error occurs, an error document is sent instead.
The content length and every <META HTTP-EQUIV=...> is added to the HTTP header before it is sent. If Embperl is executed as a subrequest or the output is going to a file, no http header is sent.
To get the best performace from Embperl, it is necessary to restrict logging to a minimum. You can drastically slow down Embperl if you enable all logging options. (This is why `make test' takes a while to run.) You should never enable dbgFlushOutput or dbgFlushLog in a production environment. More debugging options are useful for development where it doesn't matter if the request takes a little bit longer, but on a heavily-loaded server they should be disabled. Additionally the options optDisableChdir, optDisableHtmlScan, optDisableCleanup have consequences for the performance.
Also take a look at mod_perl_tuning.pod for general ideas about performance.
None known.
Under perl5.004 there are memory leaks. This is not an Embperl bug, but can cause your httpd to grow endlessly when running under mod_perl. Please upgrade to perl5.004_04 to fix this. You should also upgrade to a mod_perl version higher than 1.07_01 as soon as possible, because until 1.07_01 there is a memory leak in Apache->push_handler.
I have tested Embperl successfully
I know from other people that it works on many other UNIX systems
Please let me know if you use or test this module. Bugs, questions, suggestions for things you would find useful, etc., are discussed on the Embperl mailing list. If you have a site that is using Embperl, I would love to mention it in list of sites using Embperl (http://perl.apache.org/embperl/Sites.pod.1.html). Please drop me a mail with a short description, if your site uses Embperl.
The Embperl mailing list (embperl@perl.apache.org) is available for Embperl users and developers to share ideas, solve problems and discuss things related to Embperl To subscribe to this list, send mail to embperl-subscribe@perl.apache.org. To unsubscribe send email to embperl-unsubscribe@perl.apache.org .
There is an archive for the Embperl mailing list at http://www.ecos.de/~mailarc/embperl/
For mod_perl related questions you may search the mod_perl mailing list archive at http://forum.swarthmore.edu/epigone/modperl
You can get free support on the mod_perl mailing list (see above). If you need commercial support, ecos can provide it for you. We offer:
You can reach us via http://www.ecos.de or info@ecos.de For more information about our support see
http://www.ecos.de/x/index.htm/support/eng_r_support.htm
If you use and like Embperl and want to support it's ongoing developement you have two possibilities:
mod_perl http://perl.apache.org/
mod_perl FAQ http://perl.apache.org/faq
Embperl http://perl.apache.org/embperl/
Embperl (german) http://www.ecos.de/embperl/
DBIx::Recordset ftp://ftp.dev.ecos.de/pub/perl/dbi
apache web server http://www.apache.org/
ben-ssl (free httpsd) http://www.apache-ssl.org/
stronghold (commerical httpsd) http://www.c2.net/
europe http://www.eu.c2.net/
other Apache modules http://perl.apache.org/src/apache-modlist.html
mod_perl http://www.perl.com/CPAN/modules/by-module/Apache Embperl ftp://ftp.dev.ecos.de/pub/perl/embperl DBIx::Recordset ftp://ftp.dev.ecos.de/pub/perl/dbi
Win NT/95/98 binarys
Apache/perl/
mod_perl/Embperl ftp://theoryx5.uwinnipeg.ca/pub/other/
europe http://www.robert.cz/misc/
RPM
source ftp://ftp.akopia.com/pub/support/srpm/
binary redhat 6.0 ftp://ftp.akopia.com/pub/support/6.0/
binary redhat 6.1 ftp://ftp.akopia.com/pub/support/6.1/
Debian packages http://www.cse.unsw.edu.au/~gusl/embperl
PPM for ActiveState http://theoryx5.uwinnipeg.ca/ppmpackages/
The latest developments are available via CVS. Look at ``perldoc CVS.pod'' for a detailed description.
From: Erik Arneson [erik@mind.net]
Here's the amount of documentation I've got right now.
They need to get mmm.el from this URL: http://members.tripod.com/gchen2/xemacs/
Then download my mmm-embperl.el from this one: http://www.aarg.net/erik/mmm-embperl.el
The documentation for using these is included in those two elisp files.
Vim Syntaxfile for Vim 5.x & 6.x from Lukas Zapletal with syntax highliting for JavaScript, VBScript, Perl+Embperl, CSS and HTML, yellow background for Perl`s code (like M$ Interdev) and working Perl folding can be found at http://vim.sourceforge.net/scripts/search_results.php?keywords=Embperl
Vim Syntaxfile from Steve Willer can be found at http://www.interlog.com/~willer/embperl.vim
Vim Syntaxfile from Kee Hinckley can be found at http://www.somewhere.com/software/
Dreamweaver extension which tells Dreamweaver not to touch Embperl code can be found at http://www.somewhere.com/software/
G. Richter (richter@dev.ecos.de)
perl(1), mod_perl, Apache httpd
|
HTML::Embperl - Building dynamic Websites with Perl |