After purchasing a wildcard SSL certificate I was hoping to be able to redirect all traffic from http://example.com to https://www.example.com. There were two main goals which were to redirect all traffic to www.example.com and to require HTTPS. There is one flaw with this plan as it requires two valid certificates to work 100% of the time. The one scenario where it will not work is if a user types https://example.cominto a browser and you do not have a valid SSL certificate for example.com and instead only have a wildcard SSL certificate for *.example.com. The user will be prompted with an invalid certificate message when visiting the https://example.com domain.

The problem here is that the SSL handshake is happening before you are able to complete a redirect on the request. The only way to resolve this issue is to purchase two certificates to handle *.example.com and example.com. If you don’t mind the possibility of users typing in https://example.comand getting an invalid certificate message then purchasing a wildcard certificate only will cover you in 99% of situations.

This is a mini how to that shows how to edit svn:externals from a UNIX shell or from TortoiseSVN on Windows. Follow the simple directions below to modify the svn:externals and commit to your SVN repository. I performed the below two sets of steps on CentOS 5.2 for the Linux steps and on Windows XP Service Pack 3 for the Windows steps.

svn:externals from UNIX/Linux shell

1. Set SVN_EDITOR: First you will need to set the SVN_EDITOR to your favorite UNIX/Linux editor. I perfer vi so following this exact will open the svn:externals in the vi editor. If you want to use a different editory simply change /bin/vi to the path of your favorite editor.

[root@server ~]$ SVN_EDITOR='"/bin/vi"'
[root@server ~]$ export SVN_EDITOR

Read the rest of this entry »