Networking Protocol Question

Brian Carpenter

if i have a product that can do the following,Built in networking applications DHCP client, UDP, DNS client , ARP, ICMP ping, FTP, TELNET,
HTTP. Can i not assume that it can also do HTTPS? Is HTTPS just another layer on HTTP?

Coder96

In short, no. You cannot assume it's there.

Considering the protocols not listed ssh, scp, sftp and https. Any half good marketing person would not miss putting more features on a list. It's more than likely safe to say https is not supported.

The "s" in these cases are for encryption. Which does take more ram and processing power than with just the plain protocols.

kwinn

As coder96 says, you can not assume it is there. Virtually all companies will list every protocol they can possibly justify adding to the list even if it is not completely supported. Think of it as corporate chest thumping. If it is not listed you can be certain it is not supported. HTTP is Hyper Text Transport Protocol, which is used for the web. HTTPS is Hyper Text Transport Protocol Secure, which is the encrypted version.

LoopyByteloose

Bargain purchases are generally defined as good and bad by what is missing in the feature list - buyer beware.

Sellers love people that will just assume it works.

I once had a 1953 GMC pickup without engine that I had to get rid of immediately (landlord threatening eviction). A guy with a 1953 Chevy pickup had hit a tree and needed a new front. Of course I said 'it could work', but to this day I still wonder if he ever got his half Chevy/half GMC assembled. The price was right, free if gone today.

localroger

It's definitely not supported; as coder96 says it would be listed if it were. HTTPS uses a completely different port (443 instead of 80) and requires significant processing to fetch key certificates and perform the encryption/decryption.