When attempting to sync a repo to a server or to your desktop you will receive an error if the certificate being used to protect the HTTPS repository URL is not issued by the proper authority. Many companies generate their own certificates for repository URL’s especially if the repository is primary used internally. In this example I was attempting to sync a repository using SVN to a folder on the desktop of my Macbook Pro running OSX Mountain Lion. Below I describe the error in more detail followed by resolution to the svn certificate error.
If you have ClientExec installed in a sub-directory say /clientexec and want to require HTTPS only for ClientExec the easiest way to accomplish this is by putting a .htaccess file inside of the sub directory itself. There are numerous solutions to this posted as CE Knowledge Base Articles and within the CE forums but many of them did not work for me so I wanted to post the solution that worked on setup using CentOS as the operating system and using Apache/PHP/MySQL on that platform.
Network stress testing is taken for granted sometimes however it is extremely useful in many aspects of a network. Typically when someone is thinking of stress testing something technology related they are thinking of stress testing a web application of some sort however it is beneficial to also stress test every piece of network hardware from the firewall to the web server that the application is running on to make sure there are no weaknesses once packets touch your network. With that said there are some great applications within Backtrack that provide stress testing capabilities such as siege which is classified as a HTTP/HTTPS Stress Tester which depending on the location you test from could also test network hardware between the Internet and the web server running the application being tested.
The below article is the first in a series of articles to help get you more familiar with the BigIP BigPipe commands used to manage an LTM VE or Local Traffic Manager Virtual Edition installed in VMWare Player as noted in this article. After following the steps in this article you will have created two VLAN’s (Virtual Local Area Networks) and added an IP address to each VLAN which will be the foundation of the series of articles that will help you setup and configure your LTM VE to do basic load balancing followed by other articles that build on that foundation. The future articles will become more in depth by first taking you through basic troubleshooting steps using and overtime using more advanced techniques for troubleshooting issues on a BigIP Local Traffic Manager.
The other day while configuring a Asus RT-N16 wireless router we had installed DD-WRT software on I decided to turn off HTTP access to the web admin interface. After making this change I got pulled away to test something else and never tested it so I was surprised when I attempted to login today and I was unable to login to the DD-WRT web interface using HTTP or HTTPS. Turns out something was not allowing HTTPS to start and since I had disabled HTTP the wireless router was no longer listening on port 80 or port 443. Below is information on how to start Apache after logging into a wireless router running DD-WRT either via SSH or via telnet.