News for hackers. Stuff that matters.
Re:Coinbase Merchant Data Leak? by ntumlin on Friday April 05, 2013 @09:31AM (#5498263)
What's a good alternative to robots.txt?
Re:Coinbase Merchant Data Leak? by espo on Friday April 05, 2013 @09:38AM (#5498309)
Proper access control on your web site.
Re:Coinbase Merchant Data Leak? by Cthulhu_ on Friday April 05, 2013 @09:57AM (#5498418)
Simply not showing the transaction if you're not logged in and not the user belonging to the transaction?
Re:Coinbase Merchant Data Leak? by enoptix on Friday April 05, 2013 @09:58AM (#5498420)
You can also specify a meta robots tag inside the page HTML. If you want to block a lot of pages, your best bet would be to add it to your master layout or template. You get the same effect of blocking on robots.txt but without exposing a list of blocked pages.

The downside is that Google will still crawl the page and use your bandwidth, but the page won't be indexed.

Re:Coinbase Merchant Data Leak? by JimWestergren on Friday April 05, 2013 @11:25AM (#5498953)
I would suggest both these two: Check the user agent for bots and if it is a bot send a 404 header and exit before page needs to load. Also add a meta noindex just in case. Robots.txt DOES NOT prevent indexing, just crawling.
Re:Coinbase Merchant Data Leak? by dpcx on Friday April 05, 2013 @09:38AM (#5498302)
Blocking access to googlebot for those pages is the easiest. But robots.txt would work, if you just did

Ignore /checkouts/