Hi, as stated above the Apache2 + mod_perl approach to serving web content generated by your Perl script is *very* outdated. If you are setting up a server in a new environment, or a new app in an existing server environment, I'd recommend against that framework unless there is some specific reason why it must be used.
I used Apache + mod_perl for years, but haven't used it for more years. For a simple, intuitive, modern Perlish approach I'd recommend setting up a lightweight Perl Dancer app. Here is the Dancer2 deployment guide including instructions for running under Apache if that's your production web server. Try it; you'll be serving requests with your code before you figure out that VHost mod_perl config :-)
Hope this helps!
The way forward always starts with a minimal test.
Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
Want more info? How to link
or How to display code and escape characters
are good places to start.