Thanks to all who responded on this question. [ I am now using curl -k to test my self-certified SSL connections :) ]
I have also concluded that the standard way to have one `section' of a site handled via SSL is to actually have a separate VirtualHost ... maybe this is obvious but I don't think the documentation made it so. In particular, I think http://httpd.apache.org/docs-2.0/ssl/ssl_faq.html#vhosts2 should be placed more prominently in an introduction area. Anways, I now have a separate virtual host listening on 443 and serving https. It is supposed to be only used for the /secure directory, so I am trying various methods of dealing with relative links, images, etc. I wanted to build a mod_perl PerlPostReadRequest URI translation handler to switch back and forth between protocols, but there's a bug or something with APR::URI at the minute so that attempt is on hold. I used the recommended mod_rewrite recipe (http://httpd.apache.org/docs-2.0/ssl/ssl_faq.html#relative) but didn;t like the extra taglet on the end of my tags (they already get processed by TT2 and sometimes other stuff), so I went with: RewriteCond %{REQUEST_URI} !/secure/ RewriteRule ^/(.*)$ http://www.ladyraquel.com:8080/$1 [R,L] in the secure server and RewriteCond %{REQUEST_URI} /secure/ RewriteRule ^/(.*)$ https://secure.ladyraquel.com:8443/$1 [R,L] in the plain one. HOWEVER, in both cases I encountered problems with Netscape Navigator 4.08 warning about the >redirect< to the non-secure page. Any suggestions about this? Thanks, - nick -- ~~~~~~~~~~~~~~~~~~~~ Nick Tonkin {|8^)> ______________________________________________________________________ Apache Interface to OpenSSL (mod_ssl) www.modssl.org User Support Mailing List [EMAIL PROTECTED] Automated List Manager [EMAIL PROTECTED]
