But yeah, the below is right. Transport layer

is where your request to access the pink un site (in various packets), bounces from router to router until it arrives at the pink un's web server. When it gets there, the pink un server will need to understand the request, which it does from the packet request for http port 80)

Pink uns web server first acknowledgement back to say it's received the request, then sends the page request back through the routers, bouncing around until it's received back to you

Now, what's happened with malky is, the pink un's web server is wobbling for a second, so instead of showing the content on the page, it's just show the url, and the 80 in the url, is the pink un's web server's way of saying "hello, the request and transport is all find accross the internets, but I'm struggling to access port 80 on the pink un's web server, I'll try and send it to in time"

All that awesomeness usually happens in a matter of seconds, specially if you think that you might log onto a Aussie site. You're little packets of requests bounce accross various routers around the world, and back, in seconds

When the destination is offline, that's where you get transport acknowledgements back saying "we're cool, I've just been to Australia for you, but they wouldn't let me in, so here's your 404 error to prove I'm working but the destination server isn't"

Brilliant innit

Posted By: pants, Jun 1, 15:40:44