An SSL, or Secure Socket Layer, is technology that has been developed that allows web browsers and web servers to communicate over a secured connection.

The system uses cryptography that uses two keys to encrypt data  a public key known to everyone and a private or secret key known only to the recipient of the message. It’s a way to encrypt data, like credit cards numbers (as well other personally identifiable information), which prevents the "bad guys" from stealing your information for malicious intent.

The recently introduced SSL v3 improved upon SSL v2 by adding SHA-1 based ciphers, and support for certificate authentication. SSL v2 was known to be flawed in a variety of ways. Identical cryptographic keys are used for message authentication and encryption. The older version did not have any protection for the handshake, meaning a Man-in-the-middle downgrade attack could go undetected.

SSL has recently been succeeded by Transport Layer Security (TLS), which is based on SSL and is included as part of both the Microsoft and Netscape browsers and most Web server products. SSL uses the public-and-private key encryption system from RSA, which also includes the use of a digital certificate.

SSL-enabled client software can use standard techniques of public-key cryptography to check that a server's certificate and public ID are valid and have been issued by a certificate authority (CA) listed in the client's list of trusted CAs. Client authentication allows a server to confirm a user's identity. It’s a way to assure a client that they are dealing with the real server they intended to connect to. It can prevent any unauthorized clients from connecting to the server, preventing anyone from meddling with data going to or coming from the server.

From the very beginning SSL was designed to provide security between client and server, and to avoid any kind of 3-way man-in-the-middle attack.

Conceptually it’s quite simple: it negotiates the cryptography algorithms and keys between two sides of a communication, and establishes an encrypted tunnel through which other protocols (like HTTP) can be transported. It can also be easily passed through firewalls and proxies, as well as through NAT (Network Address Translation) without issues.

I think the biggest mistake many of us make when we set out to build a website to make money is not to think out clearly how we are going to achieve this under our given set of circumstances.

We immediately jump on whatever bad wagon promises the best opportunity and hope to be able to achieve the same results. While hope is always nice it is action that will bring results. This is why it is imperative at the outset for you to figure out what you are prepared to do and how you are going to go about doing it.

For example list your strengths and what you are comfortable doing. Then you are going to look for ways and opportunities that will compliment your strengths.

If I had done this years ago I would have been a lot more successful. What I did instead was jump on the latest greatest opportunity, then when I would get the material I would be disappointed because many of the techniques listed where not in my field of expertise.

For example it would involve me having to cold call people to make sales and this is something I hate to do. So your first objective when setting out to build a website is to build it around a subject that you have some relationship with. Basically something that interests you.

Start out broad and be prepared to be taken down different paths that may yield more positive results in other words do not be too ridged.

Research is critical the more time spent researching the better your chances of success. Visit forums relative to your topics of choice and see what people are looking for - then with this information start to structure your site.

There are many site builders out there that can help. The one I used took care of the hosting and also helped me to market the site. This was very helpful especially starting out.

To conclude figure out what you want to do then be prepared to be adaptable based upon what the market demands. Then build a site that addresses their needs and provides solutions and you will make money.

Just what is a 301 Redirect?

There seems to be a lot of confusion as to what to do when you move, delete, or want to redirect incoming web traffic from an 'old' web page to a 'new' web page. A 301 redirect is the most efficient method for web page redirection from an old web page to a new web page location. There is also some confusion as to how to handle the complete move or redirection from one web domain to another web domain. According to Google, "If you need to change the URL of a page as it is shown in search engine results, we recommended that you use a server-side 301 redirect instead."

How to Set Up a 301 Redirect

Depending on your web environment, there are several methods to set up a 301 redirect. A 301 redirect is not that hard to implement and it should preserve your search engine rankings for that particular page or web domain.

.htaccess 301 Redirection

The .htaccess file needs to be placed in the root directory of your old website. In this example, we are redirecting incoming web traffic from an old domain to a new domain.

Options +FollowSymLinks

RewriteEngine on

RewriteRule (.*) http://www.newdomain.com/$1 [R=301,L]

The .htaccess file is the most common method used for 301 web site redirection.

PHP 301 Redirection

You would place this code in a file at the old location.

Header( "HTTP/1.1 301 Moved Permanently" );

Header( "Location: http://www.new_location.com" );?>

IIS 301 Redirection

• In Internet Services Manager, you need to right click on the file or folder you wish to redirect
• Select the radio button titled "a redirection to a URL".
• Enter the redirection web page
• Check "The exact URL entered above" and the "A permanent redirection for this resource"
• Click on 'Apply'

That is all there is to it.

There are other methods in addition to set up a 301 redirection which include coding for ASP, ASP.NET, Java, CGI, Cold Fusion and Ruby on Rails. The above are the most common that I've encountered. When set up correctly, a 301 redirect will preserve your search engine rankings when it is necessary to move files around or switch, or consolidate, domain names.