Abusing HTTP Status Codes To Expose Private Info

Want to read Slashdot from your mobile device? Point it at m.slashdot.org and keep reading!

Abusing HTTP Status Codes To Expose Private Info 133

Posted by CmdrTaco on Wednesday January 26, 2011 @11:09AM from the i-see-what-you-did-there dept.

An anonymous reader writes "Here's a neat technique for testing if people are logged into other websites. Examples for Facebook, Twitter, GMail and Digg are provided." Like we needed more reasons to use the Chrome incognito function.

This discussion has been archived. No new comments can be posted.

Abusing HTTP Status Codes To Expose Private Info

Search 133 Comments Log In/Create an Account

Comments Filter:

There may be more comments in this discussion. Without JavaScript enabled, you might want to turn on Classic Discussion System in your preferences instead.

Abusing HTTP Status Codes To Expose Private Info 133

Abusing HTTP Status Codes To Expose Private Info More Login

Abusing HTTP Status Codes To Expose Private Info

Related Links Top of the: day, week, month.

Slashdot Top Deals

Slashdot