Jump to content
Posted 11 February 2009 - 11:08 PM
Posted 12 February 2009 - 04:23 AM
Primary system: Motherboard: ASUS M4A89GTD PRO/USB3, Processor: AMD Phenom II x4 945, Memory: 16 gigs of Patriot G2 DDR3 1600, Video: AMD Sapphire Nitro R9 380, Storage: 1 WD 500 gig HD, 1 Hitachi 500 gig HD, and Power supply: Coolermaster 750 watt, OS: Windows 10 64 bit.
Media Center: Motherboard: Gigabyte mp61p-S3, Processor: AMD Athlon 64 x2 6000+, Memory: 6 gigs Patriot DDR2 800, Video: Gigabyte GeForce GT730, Storage: 500 gig Hitachi, PSU: Seasonic M1211 620W full modular, OS: Windows 10.
If I don't reply within 24 hours of your reply, feel free to send me a pm.
Posted 12 February 2009 - 08:01 AM
Posted 12 February 2009 - 08:04 AM
[ more bits and pieces | refresh this page | view server headers ]
When your browser requests a web page from a server via HTTP, it sends a set of headers with various bits of information about itself. Below you can see the headers sent by your browser.
HTTP headers supplied by your browser (d-206-53-78-230.cpe.metrocast.net):
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:126.96.36.199) Gecko/2009011913 Firefox/3.0.6
NB: If you see a header named "Referer" and are wondering why it's spelled incorrectly, it's because the original specification for HTTP/1.0 got it wrong, OK? Please stop asking me about this. From RFC 2616: "The Referer[sic] request-header field allows the client to specify, for the server's benefit, the address (URI) of the resource from which the Request-URI was obtained (the "referrer", although the header field is misspelled.)".
Edited by usasma, 12 February 2009 - 08:06 AM.
redid the quote to show BC as the referer
Posted 12 February 2009 - 09:50 AM
Posted 12 February 2009 - 10:07 AM
Posted 12 February 2009 - 01:26 PM
0 members, 0 guests, 0 anonymous users