phpinfo() Phones Home

So I was doing some client work today when I noticed something somewhat disturbing; phpinfo() has a logo that sends data back to I’m not sure exactly what the data is, but here’s the offending markup.

<img border="0" src="?=PHPE9568F34-D428-11d2-A769-00AA001ACF42" alt="PHP Logo" />

The somewhat more disturbing part is that this image also sets a cookie. The cookie appears to hold both my country and the IP address of the requesting agent.


I’ve looked at a few scripts and found that the src of the image file appears to change slightly between installations. I’m sure it’s nothing malicious, but it is a bit odd.

Anyone else know anything about this?

Birthday Mystery

As I pointed out in a previous post, my birthday was on March 15th. I turned the ripe old age of 26 and had a good time doing so. At any rate, a few days ago I check my mail and find a birthday card which was postmarked from Columbus, OH. All it says is “Happy 26th! Jason”. I know three Jasons and none of them would be likely to send me a birthday card and I know for a fact that two of them don’t live anywhere near Columbus, OH. The only thing I can think is that someone who visits this site sent it to me.

If that’s the case then please send me an email to so I can thank you for the card.

March 14th, 2006

That’s when it’s all over and Lauren and I will officially be no more in the eyes of the law. It’s at this point I’d like to lament the divorce laws of Washington for making a couple of young kids wait months before finalizing everything. Seriously, it’s just stupid.

The next day, March 15th, is my birthday. I’ll be turning the ripe old age of 26. 30 is right around the corner. A few days later I’ll be at a local Irish pub enjoying green beer in celebration of the fact that I was not named Patrick as my parents had planned if I had been born on March 17th.

Other than the upcoming busy week things are going fairly well. I have lots of work sitting in front of me, we move facilities and started upgrading some of our equipment and I’m kicking myself for not hitting 24 inches of fresh powder with Garren at Stephen’s Pass yesterday. Oh well, at least it’s sunny out today.

Pistons beat the buzzer

Billups and Wallace at the scorer's table

On Friday I ventured down to Key Arena with Lauren. The deal was that if she couldn’t find someone to go to the game with then we’d go together. As luck would have it my boss was there with a friend as well sitting in the first row with four empty seats next to him. I think everyone knows where this is going. Lauren and I were able to make our down to the first row at center court. In the picture above you’ll see Chauncey Billups and Rasheed Wallace each sitting about 8 feet away from us and the guy in the white shirt is Bill Laimbeer.

Josh, this is the point where you ball up in the fetal position as the only response to your overwhelming sense of jealousy and rage at the fact you weren’t there with me drinking a beer and sitting in the awe that is Hamilton hitting a buzzer beater with 0.2 seconds left on the clock.

DB_Virtual 0.0.7

This is a critical update for anyone using DB_Virtual. I wasn’t passing $onoff onto the master DB::autoCommit() function which would effectively break transactions.

Additionally, I was noticing strange behavior when I would do a couple of INSERT queries and then immediately query for that data set after the transaction had committed. What was happening was that the records were created on the master, but the subsequent SELECT was going to the slave before they had propagated to the slave. Basically master/slave latency was breaking the SELECT queries. As a result, I’ve added DB_Virtual::queryMaster(), which acts just like DB::query(), so you can query the master node in such situations.

  • Fixed a bug in DB_Virtual::autoCommit() that wasn’t passing $onoff to the master’s DB::autoCommit()
  • Added DB_Virtual::queryMaster() so you can send queries directly to the master

Download DB_Virtual 0.0.7

Framework 0.1.1

A minor release that addresses a few small bugs and addresses some minor issues with where the database connection is stored. A recommended upgrade for anyone using Framework.

  • Fixed bug in query logic in Framework_User::__construct()
  • Added Framework_Auth_User
  • Added DB::disconnect() to Framework::stop()
  • Moved DB connection to Framework::$db so static methods can access the DB connection

Download Framework 0.1.1