MikeW
22nd June 2007, 01:44 PM
Hi Viktor,
For security purposes, I want to put the password authentication on a certificate-protected SSL connection, rather than plain HTTP. This looks to mean putting the whole application under SSL, rather than just the login.
I'm also setting it up where my customer "users" don't have access to the application, so will never log in - in fact never see the login page normally.
I can play with the login page to remove the submit-ticket section, and place
it in an out-of-the-way URL. For example:
https://secure.example.com/supportapps/supportcenter
But... I'd also like to present the "submit-ticket" form on a rather more standard HTTP page - perhaps
http://support.example.com/submitticket.php
I've tried experimenting with duplicating the code, but pointing at the same DB, but there is a mixture of behaviour. Some actions go to a relative URL, and some seem to pick up the URL defined during configuration, that is sitting in the DB.
Is it possible to do a split of the application in this way?
Or is this something best achieved with fiddling with apache rewrite configuration?
Cheers,
Mike
For security purposes, I want to put the password authentication on a certificate-protected SSL connection, rather than plain HTTP. This looks to mean putting the whole application under SSL, rather than just the login.
I'm also setting it up where my customer "users" don't have access to the application, so will never log in - in fact never see the login page normally.
I can play with the login page to remove the submit-ticket section, and place
it in an out-of-the-way URL. For example:
https://secure.example.com/supportapps/supportcenter
But... I'd also like to present the "submit-ticket" form on a rather more standard HTTP page - perhaps
http://support.example.com/submitticket.php
I've tried experimenting with duplicating the code, but pointing at the same DB, but there is a mixture of behaviour. Some actions go to a relative URL, and some seem to pick up the URL defined during configuration, that is sitting in the DB.
Is it possible to do a split of the application in this way?
Or is this something best achieved with fiddling with apache rewrite configuration?
Cheers,
Mike