A long list of forum and content management system software is listed in /forum/remark,7962246
C and C++ are very powerful languages that have withstood the test of time. They can be hard to learn. Most commercial programs are written in C or C++ languages. The C++ language evoved from C in order to support "object oriented" programming. C is the language of choice if you are running in embedded devices or wherever resources are scarce. For example, much of Linux is written C.
Visual Basic is a Microsoft technology that is easy to learn. While it is a good language for beginners, it's performance and lack of control (compared with C++) can be a problem. As a result, there aren't very many professional programs released using VB. Microsoft IIS comes with Active Server Pages (ASP), which is most often used with a Visual Basic variant called VBScript.
Perl is a language that is also found on many Unixy systems. It is excellent at string parsing. This site is written in Perl.
Java is a language created to run in embedded devices. It features object oriented programming with automatic memory management and "write once run anywhere" operation. Java is becoming very popular as the "back end" to large web sites.
HTML 4.01 was the last major HTML standard. It was released in December, 1999. The next generation is called XHTML, which finally arrived in 2002. An XHTML file is a special type of XML document that looks very much like HTML 4.01, and appears to be HTML 4.01 to older browsers.
If you want to incorporate graphics into the web pages, you should become familiar with the different formats used on web pages, such as .GIF, .JPG, and .PNG. There are several good utilities available to assist you in converting graphics for use on the web.
There are other "back end" languages, such as PHP, ASP, and Cold Fusion, that allow you to create dynamic (changing) web pages based on content that typically comes from some sort of database. These languages typically "piggyback" onto the HTML pages, allowing you to put programming information directly into your web pages.
Also see /faq/6870
Compact Index of HTML Tags for quick reference. It does have one drawback--the tags haven't been updated to HTML 4/XHTML 1 standards.
For more in-depth and current information, these are very good, just not as compact:
An SSL-encrypted HTTP session is initated by using the "https" method on the URL (Uniform Resource Locator).
Your browser connects to the web server and begins a complicated dialog to establish a secure channel and verify the site's identity.
The channel is secured using a "handshake" protocol that creates a Session. The web site server sends its "certificate" to the browser. The browser then tries to verify the validity of the certificate. If the certificate is valid, the handshake protocol performs a key exchange so that each end (the web site and server) have keys to encrypt and decrypt the data.
If you connect to a site with https: and you get a warning about the certificate, it means your web browser was unable to authenticate the web server's certificate with a recognized certificate authority. This means you cannot be absolutely certain you are talking to who you think you are. If you are certain, you can still proceed and establish the SSL Session. Your data will be encrypted just the same, but you will not have verified the remote web site server's identity.
It's unlikely (but technically possible) to steal personal information like passwords and credit card numbers by listening into web site traffic. The encryption of the data means that as web site data passes from router to router, nobody can read your credit card information until it gets through the Internet and safely to your web server.
Web site pages encrypted with a 128-bit session key are considered "computationally secure". This means that with current technology, the 128 bit session key cannot be cracked in anything less than several days.
An interesting feature of the SSL protocol allows either the client or server to request new encryption keys at any time. Nobody does this now, but it would be an extra measure of protection when computers get fast enough to crack the 128-bit SSL key.
Feedback received on this FAQ entry:
Please submit packages not listed. Last updated January 24, 2006.
When users try to access content on a server that is running Internet Information Services (IIS) through HTTP or File Transfer Protocol (FTP), IIS returns a numeric code that indicates the status of the request. This status code is recorded in the IIS log, and it may also be displayed in the Web browser or FTP client. The status code can indicate whether a particular request is successful or unsuccessful and can also reveal the exact reason why a request is unsuccessful.
»support.microsoft.com/default.as ··· s;318380