Http: and https:
Do not bother to offer surfers internet addresses that contain the "www" part. Writing it is a waste of surfing time.
There are certain search engine registration functions out there on the internet that allow you to register with them using the "http://www." or "https://www." prefix of your internet address.
Example:
http://www.example.eu/
In reality, some search engines and internet transmission links will know about your internet presence, within a few days after your domain name has been attached to your domain on your server. That means that a domain name written in alpha numeric characters is the human readable pseudonym for a specific storage area on a specific computer that is configured by it's software content to be a so called server. Server means that it's main purpose is to supply data to other computers. It can also do other types of processing, if it has also been configured to do other things.
See Sitemap and Robots Text about how to stop search engines from documenting your website, before you want them to.
You do not want search engines to construct a premature opinion of your website and not want to include it in their search results.
The HTTP Protocol:
This is the Hyper Text Transport Protocol (http).
"http:" is almost always available on computers that can communicate with other computers.
As it's name indicates, it started it's existence on telecommunication lines as a method of transferring text from one place to another.
As time progressed, it has been expanded so that it will transport just about any kind of data from one place to the next on a telecommunication line.
In reality, for the internet, all information is the same and transferred as blocks of data, differentiations is done at the individual computer level.
Web browsers use the extension in filenames to decide what to do with files.
Example: The content of *.html and *.php files are interpreted and placed in the visual component of the web browser. That content is shown on a computer screen.
Other types of files are placed in the "download" directory, so that surfers can make decisions about them.
The FTP Protocol:
The "ftp" protocol works in both direction, but for most web server owners, the upload function is the most relevant, because download can be done more often using the http protocol.
The "ftp" protocol is sometimes deactivated completely by server providers and replaced by the "sftp" version.
The HTTPS and SFTP:
As far as "https" and "sftp" are concerned, they are often called secure data transport protocols.
Do not misunderstand what is actually going on:
All data that is on a computer or transported from one main point to the next is encoded in some way.
The actual problem is, how does one know when an error has occurred during a transmission and if it can be found, can that error be corrected.
Contrary to some common beliefs, the problem has absolutely nothing to do with trust, fault, blame or keeping something secret.
Example:
If an internet shop sends a number that represents a money value somewhere, one may want to do everything in ones power to prevent that value from being modified by random disturbances in the signal path.
"https" error detection is used in the signal path between a user's computer and the next internet telecommunication station. The same is valid for the server side. It is not specific to any particular web browser.
If you do not have an encoder/decoder for it, it is not your data.
Some people think that search engines software is setup to classify the content of web pages as low value, if "https" is not used to fetch them.
We do not have any information about how good "https" is at finding and correcting errors or even asking for a re-transmission from a sender.
Example:
As far as secret or secure is concerned, remember that in normal every day life, most important of all, is the $ amount that is being transmitted. You want it to stay correct right up to the data receivers eyes.
You may very often see long and complicated internet addresses (URL) that also contain the "https:" protocol designator. That length has nothing to do with the function of the "http:" or "https:" part.
Check Sum Error Detection and Correction
1. All computer data types are in actual fact numbers.2. By adding all the numbers together as they are being sent or before they are sent, a check sum total will be available.
3. The check sum total is then sent as the last part of the transmission.
4. When the data reaches the first internet station, the same addition is carried out on the data.
5. If the resulting check sum total is different to the one that is received at the end of the transmission, than the receiver will know that there is something wrong with the connection line.
6. Our error detection example can not know which part of the data is not correct, but it can ask for a re-transmission.
7. Important: The fact that errors can be detected in normal data on different sections of transmission lines means that maintenance personnel can become aware of defects and correct them, without knowing anything about the content of transmissions.
They get knowledge of the error through the check sum as stated above. An alternate path is established for bad data lines, before maintenance personnel go out to repair them. That means that, that which is commonly called security is in fact error detection. And that is done without having to stop the use of communication lines in regular intervals in order to check if they are still fully operational.
Of course, if one has error detection and the others do not, it would not be so far fetched to claim that one has secure software transmission functions that prevent others from reading ones data while it is moving from one place to the next across communication lines.
8. The http protocol will consider it an error, if anything arrives at the web browser that is not written using the alphanumeric characters that can be reached from a keyboard.
9. Due to the fact that the http protocol was developed over a number of years, it contains special characters, symbols and combinations that are used as http interpreter instructions. If one then wanted to send a description of the interpreter language in a web page, the special characters and symbols that are being described had to be given short and unique alphanumeric identifiers, so that the http interpreter would not interpret them as instructions. Those strange short groups of alphanumeric characters that you sometimes find in html source text is therefore not security coding, it is replacement coding.
Example:
<h1> is used by the built in html programming language of a web page maker to mark the start of a main heading.
If that very same <h1> string is written by a web page maker in a web page, it would be replaced in the html source text with <h1>
< is <
> is >
The web page source text interpreter in the web browser makes the conversions and shows
< as <
> as >
That means that in html jargon, it takes 4 keyboard characters to store the "<" marker.
Also note the "&" and the ";" in the groups of four characters. They tell the interpreter where the definition of a character starts and ends. The rest inside those two markers define which character has been encoded.
Web page makers and web browsers do the complicated encoding and decoding so that one can concentrate on the content being written and the pages can be read anywhere by all.
Privacy Policy
Contact us
<= Back
SEO Tips and Tricks - Internet data transfer protocols http, ftp, https and sftp and error detection
electronic-
soft.com
soft.com
Blog Information
