• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Tim Cooke
  • Campbell Ritchie
  • Ron McLeod
  • Junilu Lacar
  • Liutauras Vilda
Sheriffs:
  • Paul Clapham
  • Jeanne Boyarsky
  • Henry Wong
Saloon Keepers:
  • Tim Moores
  • Tim Holloway
  • Stephan van Hulst
  • Piet Souris
  • Carey Brown
Bartenders:
  • Jesse Duncan
  • Frits Walraven
  • Mikalai Zaikin

HTTPS protocol?

 
Greenhorn
Posts: 26
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hi, all, since the HTTPS protocol is listed in Sun's Test Objectives, I feel like I should know more about it. As far as I know, the difference between HTTP and HTTPS and that HTTPS is built on SSL. Is there any other difference between the two? I know that HTTP is not connection based, but from Sun's "Success Guide" it is clear that HTTPS is connection based. How is HTTPS connection-based?
Thanks.
Howie
 
Ranch Hand
Posts: 142
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Actually Check out this link for SSL...
http://developer.netscape.com/docs/manuals/security/sslin/contents.htm

Actually HTTP is connection based protocol. So is HTTPS. HTTP and HTTPS are stateless protocols but NOT Connectionless.
In HTTP 1.0 for each HTTP request, say each time the user clicks a link on some page, a new socket connection was opened. So if you clicked on 10 links on a page you will have 10 HTTP connections opened for each of these requests. This was a simple but obviously not an efficient method. To overcome this in HTTP 1.0 a keep-alive header was introduced which will enable a single HTTP connection to handle multiple requests-responses.
In HTTP 1.1 the COnnection is automatically kept alive by default.
 
With a little knowledge, a cast iron skillet is non-stick and lasts a lifetime.
reply
    Bookmark Topic Watch Topic
  • New Topic