comment on

In a current application, I take any requests for a login page (where passwords might be exchanged) and route them through a secure layer. I handle it in my Apache configuration file, doing something like

<VirtualHost _default_:80>
  RedirectMatch ^(.*login\.cgi) https://www.mysite.com$1
</VirtualHost>
[download]

Then, in any link coming from the login page, I use an http: prefix to go back to a non-secure page.

This works as far as it goes, but it's rather limited and inflexible for obvious reasons. I'm developing a new application under pure mod_perl, and would like to know if there's a convenient way to do this on the fly, so that, from within a program, I can decide to use the secure sever based on anything I choose--going to a login page, or editing a certain table, or viewing a record that has "price" in it. I wasn't able to find a discussion of this in the mod_perl docs.

Thank you, wise monks.

In reply to Switching to SSL under mod_perl by jest

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> <u> <ul>
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 intervention).
Want more info? How to link or or How to display code and escape characters are good places to start.


Your skill will accomplish what the force of many cannot
	PerlMonks