They are different layers in the network model; TCP is on the transport layer - it provides an error free connection, HTTP is on the application layer and runs on top of TCP to provide hypertext services.
The above is correct. I'm still learning but the way I see it is that the web pages both on the server end and your own end are written in hypertext markup language (HTML). When your computer asks a remote computer to send you a COPY of its webpage, you establish a connection with that remote computer using an agreed protocol called TCP/IP. As I understand it, the IP part connects the IP addresses together and then the TCP part establishes a sort of virtual connection between the two. Hypertext TRANSFER protocol (HTTP) is the agreed way (protocol) in which the remote computer copies its own data, packages it up and sends it down the virtual tube created by the TCP connection, and onwards to your own computer, at which time the (now) downloaded webpage is reassembled in your web browser from the data packets. I'm not sure whether to describe the TCP as a hose-pipe and the HTTP as the water flowing in it but for newbies like me, this explanation might help get closer to the right concept.
salam http 1.0 establishes a TCP connection for each packet http 1.1 uses only one connection for all packets
tcp
qual a diferenca entre tcp/ip e ss7
TCP (CISCO CCNA - 3.2.1.3 Interaction of Protocols)
HTTP is a protocol that functions on top of TCP/IP. Theoretically, HTTP could run on top of other transport protocols of equivalent functionality, but in practice it doesn't happen as TCP and IP are matter-of-fact standards, due to a huge installed base. Basically the TCP/IP protocol pair is currently the backbone of the internet and the huge investment in settings things up for it makes it unlikely to be replaced any time soon. That being said it should be theoretically possible to have HTTP run on top of some other transport-layer protocol, but it's more likely to happen on a private network than on the Internet, if it happens at all.
the main difference between UDP and TCP is that UDP is not a reliable protocol.
HTTP works over a TCP connection.HTTP works over a TCP connection.HTTP works over a TCP connection.HTTP works over a TCP connection.
http needs a reliable mechanism to provide connectivity between the Host i.e. the web browser and the Server i.e the web server. Now TCP is the transport layer protocol that provides it reliable communication with three-way handshake mechanism it uses to connect between a client and a server. We also have UDP at transport layer but it is not reliable way of communicating. So http uses TCP at transport layer of OSI Model.
in udp there is no check for error detection as well as the packect has reached to destination or not. where as tcp takes care of all this that's why it is slower than udp.
salam http 1.0 establishes a TCP connection for each packet http 1.1 uses only one connection for all packets
tcp
TCP (also sometimes called TCP/IP)
HTTP is implemented on top of TCP.
Yes
qual a diferenca entre tcp/ip e ss7
HTTP
TCP port 80