This Screen Shot Thing Is Pretty Cool...
Senior Member
Joined: Apr 2002
Posts: 2,930
From: IL
Originally Posted by Srce94FD' date='Feb 16 2003, 01:46 AM
GET REQUEST? 
when you type www.nopistons.com in your web browser, it sends this to the web server (or something similar)
GET / HTTP/1.1
Host: www.nopistons.com
thats what it sends over the network to phinshups server.. and as it loaded the page, it would encounter more urls, like the image you posted and all the emoticons and such, which would result in additional GET requests to the server for those images... the sniffer could also store the image data... in case my employer wanted to find out if we look at **** it would be really easy.
in case you're bored, the entire HTTP/1.1 protocol is documented here:
http://www.ietf.org/rfc/rfc2616.txt
you can play with web servers speaking HTTP/1.1 by hand using the telnet program and connecting to port 80 of web serving hosts.
Thread Starter
Senior Member
Joined: Oct 2002
Posts: 5,547
Originally Posted by pengaru' date='Feb 15 2003, 07:50 PM
when you browse the web your web browser sends requests in HTTP to the web server, a sniffer listening to network traffic would look for these requests and log them.
when you type www.nopistons.com in your web browser, it sends this to the web server (or something similar)
GET / HTTP/1.1
Host: www.nopistons.com
thats what it sends over the network to phinshups server.. and as it loaded the page, it would encounter more urls, like the image you posted and all the emoticons and such, which would result in additional GET requests to the server for those images... the sniffer could also store the image data... in case my employer wanted to find out if we look at **** it would be really easy.
in case you're bored, the entire HTTP/1.1 protocol is documented here:
http://www.ietf.org/rfc/rfc2616.txt
you can play with web servers speaking HTTP/1.1 by hand using the telnet program and connecting to port 80 of web serving hosts.
when you type www.nopistons.com in your web browser, it sends this to the web server (or something similar)
GET / HTTP/1.1
Host: www.nopistons.com
thats what it sends over the network to phinshups server.. and as it loaded the page, it would encounter more urls, like the image you posted and all the emoticons and such, which would result in additional GET requests to the server for those images... the sniffer could also store the image data... in case my employer wanted to find out if we look at **** it would be really easy.
in case you're bored, the entire HTTP/1.1 protocol is documented here:
http://www.ietf.org/rfc/rfc2616.txt
you can play with web servers speaking HTTP/1.1 by hand using the telnet program and connecting to port 80 of web serving hosts.
Senior Member
Joined: Apr 2002
Posts: 2,930
From: IL
Originally Posted by Srce94FD' date='Feb 16 2003, 02:06 AM
[quote name='pengaru' date='Feb 15 2003, 07:50 PM'] when you browse the web your web browser sends requests in HTTP to the web server, a sniffer listening to network traffic would look for these requests and log them.
when you type www.nopistons.com in your web browser, it sends this to the web server (or something similar)
GET / HTTP/1.1
Host: www.nopistons.com
thats what it sends over the network to phinshups server.. and as it loaded the page, it would encounter more urls, like the image you posted and all the emoticons and such, which would result in additional GET requests to the server for those images... the sniffer could also store the image data... in case my employer wanted to find out if we look at **** it would be really easy.
in case you're bored, the entire HTTP/1.1 protocol is documented here:
http://www.ietf.org/rfc/rfc2616.txt
you can play with web servers speaking HTTP/1.1 by hand using the telnet program and connecting to port 80 of web serving hosts.
when you type www.nopistons.com in your web browser, it sends this to the web server (or something similar)
GET / HTTP/1.1
Host: www.nopistons.com
thats what it sends over the network to phinshups server.. and as it loaded the page, it would encounter more urls, like the image you posted and all the emoticons and such, which would result in additional GET requests to the server for those images... the sniffer could also store the image data... in case my employer wanted to find out if we look at **** it would be really easy.
in case you're bored, the entire HTTP/1.1 protocol is documented here:
http://www.ietf.org/rfc/rfc2616.txt
you can play with web servers speaking HTTP/1.1 by hand using the telnet program and connecting to port 80 of web serving hosts.
i have no clue
Thread Starter
Senior Member
Joined: Oct 2002
Posts: 5,547
