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…
Nagios is a great solution for monitoring hosts, networks, and services on one or more networks. Nagios will monitor as many services as needed per device and then will send an alarm if one or more services has an issue. By default Nagios monitors a bunch of services such as ICMP, HTTP, etc. but can easily be expanded by the use of plugins and other community based open source development projects where code is developed for a specific need and then shared with the development community.
Normally when debugging problems with web applications, I try to use Firefox. However, every once in awhile there is a web application that is very Internet Explorer specific and will not work in Firefox at all.
To that end, here is a list of nice tools and add-ins for Internet Explorer.
I had created a script to run ask for a couple CLI arguements and then run httperf against a server. The goal was to load test a server for HTTP and for HTTPS. I added the –ssl switch but could not verify a couple things including if httperf had been compiled with SSL support or if the –ssl was working at all.
1. Was httperf installed with SSL support?
This is an easy one. If the –ssl option exists then your httperf was compiled with SSL support. I wasn’t sure since I installed httperf via YUM in CentOS. I also tested by compiling myself and both versions had SSL support. If you do compile yourself you can check compile-dir/config.status and see if SSL support compiled properly.
The below explains the steps necessary to redirect all Litespeed HTTP (port 80) traffic to HTTPS (port 443).