What is happening at each layer as a web page request goes through the OSI Seven Layer Model?
107537
web pages use HTTP protocol which inturn uses TCP/IP not OSI.\n\nEven if you want to relate the 5 tcp/ip layers,\n\nHere is it \nApplication - HTTP (Hyper text transfer protocol)\nTransport - TCP\nInternet - IP \nDatalink- ARP (Address resolution protocol)\nPhysical - generally 802.3 10/100/1000 MBPS if you are on                              LAN
1042449
because since your on the internet your computer is passing traffic all data that your compete get comes in data packets when ever you request a web page your passing traffic whatever you do on the web your passing traffic the CPU has to process the data even if its idle and you got a web page up its still sending and recieving data
366137
http://csdl2.computer.org/persagen/DLAbsToc.jsp?resourcePath=/dl/proceedings/&toc=comp/proceedings/icip/1995/7310/03/7310toc.xml&DOI=10.1109/ICIP.1995.537702
241589
No, they are Layer 3 Protocols.
1182154
It maybe because of the Dial-Up Connection. It might be going so slow that windows thinks that its jsut not going and it cancels the request and give you some stupid error. I had that problem when I used to be on that horribly super slow dial up conenciton.
15405
Well on our ISA server there is a directory called C:&#92;Program Files&#92;Microsoft ISA Server&#92;ISALogs that holds all the traffic it has seen passing through and details IP, Destination url/IP, date/time, type of browser etc etc.\n\nCheers
1085952
that is tracked in the software that you are using for your webserver. IIS and Apache generate their own logs of all user actions. Any other web server you may be using should have logging built in. If you are looking for a program to analyze these logs check out the Webalizer. It isn't open source but it is free.\n\nhttp://www.mrunix.net/webalizer/
622371
hi\n\ncheck this link. u can get the answer\n\nhttp://www.dotnet247.com/247reference/a.aspx?u=http://www.dotnetjunkies.com/Tutorial/E02F3646-CB1C-4252-8AEC-5F485E90A231.dcik
613966
Routers are Layer 3 (Network Layer)\nHubs and Switches are Layer 2 (Data Link Layer)\n\nCheers :)
149601
THey use a product called a "load balancer" that distributes the http requests across multiple servers.  You can also do this with round-robin dns.
338401
Interconnection, an ISO standard for worldwide communications that defines a networking framework for implementing protocols in seven layers.\n\nApplication(Layer 7) \nThis layer supports application and end-user processes. Communication partners are identified, quality of service is identified, user authentication and privacy are considered, and any constraints on data syntax are identified. Everything at this layer is application-specific. This layer provides application services for file transfers, e-mail, and other network software services. Telnet and FTP are applications that exist entirely in the application level. Tiered application architectures are part of this layer. \n\nPresentation(Layer 6) \nThis layer provides independence from differences in data representation (e.g., encryption) by translating from application to network format, and vice versa. The presentation layer works to transform data into the form that the application layer can accept. This layer formats and encrypts data to be sent across a network, providing freedom from compatibility problems. It is sometimes called the syntax layer. \n\nSession(Layer 5) This layer establishes, manages and terminates connections between applications. The session layer sets up, coordinates, and terminates conversations, exchanges, and dialogues between the applications at each end. It deals with session and connection coordination. \nTransport(Layer 4)\n This layer provides transparent transfer of data between end systems, or hosts, and is responsible for end-to-end error recovery and flow control. It ensures complete data transfer. \nNetwork(Layer 3)\n This layer provides switching and routing technologies, creating logical paths, known as virtual circuits, for transmitting data from node to node. Routing and forwarding are functions of this layer, as well as addressing, internetworking, error handling, congestion control and packet sequencing. \nData Link(Layer 2) \nAt this layer, data packets are encoded and decoded into bits. It furnishes transmission protocol knowledge and management and handles errors in the physical layer, flow control and frame synchronization. The data link layer is divided into two sublayers: The Media Access Control (MAC) layer and the Logical Link Control (LLC) layer. The MAC sublayer controls how a computer on the network gains access to the data and permission to transmit it. The LLC layer controls frame synchronization, flow control and error checking. \nPhysical(Layer 1)\n This layer conveys the bit stream - electrical impulse, light or radio signal -- through the network at the electrical and mechanical level. It provides the hardware means of sending and receiving data on a carrier, including defining cables, cards and physical aspects. Fast Ethernet, RS232, and ATM are protocols with physical layer components.
832277
There are numerous possibilities for this and would require lots more information to get a specific answer for you.  Try looking at the resources here: http://compnetworking.about.com/cs/homenetworking/a/homenetguide.htm\n\nFor example, which operating systems are on the various machines?  That can make a HUGE difference if they are different (especially Windows XP Pro and Windows XP Home).
875892
http://www.rfc-editor.org/rfc/rfc3961.txt\n\n i dont really  know about it but what the hellthats everything i found
87386
According to the site "waybackmachine.org" an archive of internet pages, it holds 40 billion web pages archived from 1996 to a few months ago.\n\nThe surface web, or the publicly available documents is estimated in 2.5 million documents. The deep web, is 400 to 500 times bigger.\n\nSo the internet (just the web, not counting email, ftp, usenet, etc) is estimated at 550 billion connected web documents
497379
One can only functionally position the internet model to the ISO OSI model because basic differences exist such as: \n\nIn the internet protocol suite, a layer represents a reasonable packaging of function. \nThe ISO view, on the other hand, treats layers as rather narrow functional groups, attempting to force modularity by requiring additional layers for additional functions. \n\nIn the TCP/IP protocols, a given protocol can be used by other protocols within the same layer, whereas in the OSI model two separate layers would be defined in such circumstances. Examples of such "horizontal dependencies" are FTP, which uses the same common representation as TELNET on the "application layer," and ICMP, which uses IP for sending its datagrams on the "internetwork" layer. \n\nIn practice, what we are discussing here is the difference between a de jure standard, OSI, and a de facto standard, TCP/IP. The focus in the TCP/IP world is on agreeing on a protocol standard which can be made to work in diverse heterogeneous networks. The focus in the OSI world has always been more on the standard than the implementation of the standard. \n\nEfficiency and feasibility. The OSI norms tend to be prescriptive (for instance the "layer N" must go through "all layers below it"), whereas the TCP/IP protocols are descriptive, and leave a maximum of freedom for the implementers. One of the advantages of the TCP/IP approach is that each particular implementation can use operating system-dependent features, generally resulting in a greater efficiency (fewer CPU cycles, more throughput for similar functions), while still ensuring "interoperability" with other implementations. \nAnother way to see this is that most of the internet protocols have first been developed (coded and tested), before being "described" in an RFC (usually by the implementer) which clearly shows the feasibility of the protocols. \n\n2.14.2 The Internet World and OSI \nThe Department of Defense (DoD), funder of the original ARPANET research, made a statement on OSI in January '88, based on the Government OSI Profile (GOSIP) of April 22, 1987. \n\nThe following is an excerpt from the statement, which is published in RFC 1039 - A DoD Statement on OSI: "... It is intended to adopt the OSI protocols as a full co-standard with the DoD protocols when GOSIP is formally approved as a Federal Information Processing Standard. Two years thereafter, the OSI protocols would become the sole mandatory interoperable protocol suite; however, a capability for interoperation with DoD protocols would be provided for the expected life of systems supporting the DoD protocols. ..." \n\nA lot of study has already been done by the internet world on possible transitions and coexistence of the protocols. The following list is a series of RFCs already issued for that purpose: \n\nRFC 983 - ISO Transport Services on Top of the TCP. \nRFC 1006 - ISO Transport Services on Top of the TCP - Version 3. \nRFC 1039 - A DoD Statement on Open Systems Interconnection Protocols. \nRFC 1069 - Guidelines for the Use of Internet IP Addresses in the ISO Connectionless-Mode Network Protocol. \nRFC 1085 - ISO Presentation Services on Top of the TCP/IP-based Internets. \nRFC 1086 - ISO-TP0 Bridge between TCP and X.25. \nRFC 1090 - SMTP on X.25. \nRFC 1161 - SNMP over OSI. \nRFC 1195 - Use of OSI IS-IS for Routing in TCP/IP and Dual Environments. \nRFC 1238 - CLNS MIB for Use with Connectionless Network Protocol (ISO 8473) and End System to Intermediate System (ISO 9542). \nRFC 1240 - OSI Connectionless Transport Services on top of UDP: Version 1. \nRFC 1308 - Executive Introduction to Directory Services using the X.500 Protocol. \nRFC 1309 - Technical Overview of Directory Services using the X.500 Protocol. \nRFC 1327 - Mapping between X.400 (1988)/ISO 10021 and RFC 822. \nRFC 1328 - X.400 1988 to 1984 Downgrading. \nRFC 1330 - ESCC X.500/X.400 Tas
45529
Why does *what* say "request requested"?
292336
At a guess, you may have an "upstream" proxy.  Your ISP or network provider may have a proxy that is invisible to you, but still caches pages.\n\nWhat url are you trying?\n\nFor instance, do all of these return the same 2 week old content:\n\n  http://my.yahoo.com/index.html\n  http://my.yahoo.com/index.html\n  http://my.yahoo.com/index.html?test\n\nDo you have another browser you can try?  For instance you can download and install Firefox for free from \n\n  http://www.mozilla.com/