|
From: Chris M. <Chr...@te...> - 2003-01-15 21:45:44
|
Hello, Here's my question - If I want to run SSL and non SSL instances of the same site, I need to use 2 virtualhost blocks (AFAIK) so I've made a copy of my modperl solo conf file and changed it to reflect port 80 only, and I'm including them both in my httpd.conf - now when I start it up I know it's running startup.pl twice, but it seems to work OK, and when I login on one side (https, for example) I seem to carry my session over when I switch to the http side. Any downsides to this? it doesn't seem like a good idea to me but nothing else seems to work... Thanks, Chris McDaniel |
|
From: Chris W. <ch...@cw...> - 2003-01-15 22:11:07
|
Chris McDaniel wrote:
> Here's my question - If I want to run SSL and non SSL instances of the same
> site, I need to use 2 virtualhost blocks (AFAIK) so I've made a copy of my
> modperl solo conf file and changed it to reflect port 80 only, and I'm
> including them both in my httpd.conf - now when I start it up I know it's
> running startup.pl twice, but it seems to work OK, and when I login on one
> side (https, for example) I seem to carry my session over when I switch to
> the http side. Any downsides to this? it doesn't seem like a good idea to
> me but nothing else seems to work...
It always seemed to me that running an SSL-enabled mod_perl
backend is unnecessary if you have SSL-enabled lightweight apache
frontends. Plus SSL-enabling a mod_perl server is adding girth to
a process that's already pretty heavy to begin with.
The following should work without any problems:
SSL-encrypted traffic
|
--------- ------> --------------- ------> ----------
browser | lightweight-SSL proxy mod_perl
--------- <------ --------------- <------ ----------
| | | |
| +---Unencrypted traffic-+------|--|
| | | |
+--------------> ------------------- -----+ |
| | lightweight non-SSL proxy |
+<-------------- ------------------- <-------+
So the traffic between browser and SSL-enabled frontend server is
encrypted, but the traffic between frontend and backend isn't.
And since the non-SSL-enabled frontend server talks to the same
backend as the SSL-enabled frontend server you won't have any
replication issues or anything.
Of course, this means you need to run a frontend server with
mod_proxy compiled in. But this is a good idea anyway :-)
Chris
--
Chris Winters (ch...@cw...)
Building enterprise-capable snack solutions since 1988.
|
|
From: Nick T. <ni...@fb...> - 2003-01-23 09:34:41
|
I have some databases (db1, db2 etc). Some packages should work with one databasebase, some - at once with several. How to configure OI, to use this opportunity? Chris wrote about it: CW> $WEBSITE_DIR/conf/override_spops.ini: CW> [user.datasource] CW> action = add CW> value = UserDatasource CW> $WEBSITE_DIR/conf/server.ini: CW> [db_info UserDatasource] CW> db_owner = CW> username = user CW> password = password CW> dsn = dbname=userdb CW> db_name = CW> driver_name = Pg CW> sql_install = CW> long_read_len = 65536 CW> long_trunc_ok = 0 Ok! I'll describe my databases in conf/override_spops.ini & conf/server.ini as: [db_info db1] ... [db_info db2] ... But how it is necessary to configure package, that this databases is used? And how it is possible to use two different bases in package? Whether I (and whether it will be correct) can use designs of a kind "db1.table1" in struct/table1.sql for example? Sorry for my bad english :-( -- Nikollos |
|
From: Chris W. <ch...@cw...> - 2003-01-23 13:18:32
|
Nick Tkachenko wrote: > I have some databases (db1, db2 etc). > Some packages should work with one databasebase, some - at once with > several. How to configure OI, to use this opportunity? > > Ok! I'll describe my databases in conf/override_spops.ini & > conf/server.ini as: > [db_info db1] > ... > [db_info db2] > ... > > But how it is necessary to configure package, that this databases is > used? And how it is possible to use two different bases in package? > Whether I (and whether it will be correct) can use designs of a > kind "db1.table1" in struct/table1.sql for example? The package should not care what database you are using. Just set the configuration in conf/override_spops.ini, where 'myobject' is the object you have defined in your package: [myobject.datasource] action = add value = db1 or [myotherobject.datasource] action = add value = db2 And I think everything should work for creating the schemas, inserting data and fetching data. By default objects will use the datasource defined in: [datasource] default_connection_db = main So you only need to create entries in conf/override_spops.ini for the objects that are different. > Sorry for my bad english :-( Your english is much better than my russian! (It's been 10 years since school...) Chris -- Chris Winters (ch...@cw...) Building enterprise-capable snack solutions since 1988. |