SSL VPN and HTTPS relation?

in CCNA & CCENT
It might be just a weird question but i wonder something. SSL VPN is a
type of remote access VPN method which allows users to connect remotely and making a secure connection over
Internet without installing a VPN client software.HTTPS is the secure HTTP protocol running at application layer.
However, when i visited an authentication page on the Internet, URL turns
into https from http. At that time, is the only thing that changes during data
encapsulation process the https protocol instead of http?
So, how am i able to separate SSL VPN from this https?
type of remote access VPN method which allows users to connect remotely and making a secure connection over
Internet without installing a VPN client software.HTTPS is the secure HTTP protocol running at application layer.
However, when i visited an authentication page on the Internet, URL turns
into https from http. At that time, is the only thing that changes during data
encapsulation process the https protocol instead of http?
So, how am i able to separate SSL VPN from this https?
Monster PC specs(Packard Bell VR46) : Intel Celeron Dual-Core 1.2 GHz CPU , 4096 MB DDR3 RAM, Intel Media Graphics (R) 4 Family with IntelGMA 4500 M HD graphics. 
5 year-old laptop PC specs(Toshiba Satellite A210) : AMD Athlon 64 x2 1.9 GHz CPU, ATI Radeon X1200 128 MB Video Memory graphics card, 3072 MB 667 Mhz DDR2 RAM. (1 stick 2 gigabytes and 1 stick 1 gigabytes)

5 year-old laptop PC specs(Toshiba Satellite A210) : AMD Athlon 64 x2 1.9 GHz CPU, ATI Radeon X1200 128 MB Video Memory graphics card, 3072 MB 667 Mhz DDR2 RAM. (1 stick 2 gigabytes and 1 stick 1 gigabytes)
Comments
-
okplaya Member Posts: 199
What's happening is a digital certificate is being used. The digital certificate is exchanged by client/server to verify identity. The servers have public key certificates which are verified by a 3rd party (verisign, thawte, etc). Your browser provides the certificates on your behalf (done automatically). If you used HTTP to transmit your credit card # it could be intercepted and read. HTTPS uses two different encryption layers - TLS and SSL (SSL being the popular one). They do the encrypting.
Keep in mind that HTTP(S) is part of the IP protocol suite, and therefore is a routed protocol, and not a routing protocol. Encapsulation at lower layers occurs no differently as they could care less what they are carrying. Also, HTTP works over port 80, while HTTPS over 443.
So there is a bunch of things going on behind the scenes, but I hope that makes sense, and is correct lol. -
thedrama Member Posts: 291 ■□□□□□□□□□
What's happening is a digital certificate is being used. The digital certificate is exchanged by client/server to verify identity. The servers have public key certificates which are verified by a 3rd party (verisign, thawte, etc). Your browser provides the certificates on your behalf (done automatically). If you used HTTP to transmit your credit card # it could be intercepted and read. HTTPS uses two different encryption layers - TLS and SSL (SSL being the popular one). They do the encrypting.
Keep in mind that HTTP(S) is part of the IP protocol suite, and therefore is a routed protocol, and not a routing protocol. Encapsulation at lower layers occurs no differently as they could care less what they are carrying. Also, HTTP works over port 80, while HTTPS over 443.
So there is a bunch of things going on behind the scenes, but I hope that makes sense, and is correct lol.
So, if the https protocol is maintained at the application layer, no more protocols will be used at lower layers as in http?
In addition, when the https is the case, can we mention about there is a VPN?Monster PC specs(Packard Bell VR46) : Intel Celeron Dual-Core 1.2 GHz CPU , 4096 MB DDR3 RAM, Intel Media Graphics (R) 4 Family with IntelGMA 4500 M HD graphics.
5 year-old laptop PC specs(Toshiba Satellite A210) : AMD Athlon 64 x2 1.9 GHz CPU, ATI Radeon X1200 128 MB Video Memory graphics card, 3072 MB 667 Mhz DDR2 RAM. (1 stick 2 gigabytes and 1 stick 1 gigabytes)