844 karma · joined January 8, 2011
You can just as easily use the traditional unittest.TestCase methods:
self.assertEqual(HTTPretty.last_request.querystring, "whatever")
self.assertEqual(HTTPretty.last_request.method, HTTPretty.GET)
That is what I do in my tests.I've never heard of meteor before, and it's likely that many of the people who are reading the article haven't either.
Yes the site is HTTPS, but anyone can buy an SSL certificate for any purpose. It's not even a case of being MITM'd.
Basically we're telling people "read this blog post, run this curl command that runs some random shell script from this server you've never heard of before".
That's a very different from installing packages from your development community's package server, your OS's package repository, or an app store.
I know it's not possible to fully inspect all the code we run, but I'd rather we didn't encourage the habit of entirely disregarding it.
I really wish people would stop giving instructions like this. Despite all the focus on web security and sandboxing, we continue to instruct people to run arbitrary code on their user account.
People should at least give any shell script they download from the internet a cursory look to see if it's doing what it should be doing instead of blindly executing the response from an HTTP request.
For any given piece of gear in your server room there is likely a massive list of firmware bugs for it and its subcomponents. Sometimes they are fixed, sometimes not. When you run in to one that affects and need to deploy a firmware fix to dozens or hundreds of servers, it's not a whole lot of fun.
The thief had actually given him the serial number of the bike, which he checked in the online police database and it returned no hits. The catch was that the thief slightly altered the serial number so that it wouldn't yield any hits. When he went to actually look at the bike he didn't notice the subtle difference in the serial number and assumed it to be legit.