Run-in with Beaver, PA Police Department

I’m writing after a very long and scary night in an encounter with the Beaver police department in Pennsylvania.

My dad and I attended the 10pm showing of Star Trek at the Cinemark Center Township Theater near Beaver Valley Mall. All went well until our trip home. On the way home, I took my normal exit to cut through Vanport and Midland to take my dad home in Ohio.

Directly off of the exit, I encountered something I have never seen before. Having lived in Ohio, North Carolina, South Carolina, and Washington State, I have never encountered a “sobriety check point“. Am I the only one who has reached the age of 33 without this “pleasure”? It was a foreign concept to me so when I approached the officer and he asked me for my license, I was taken aback. I hadn’t done anything wrong, and my “sobriety” can be ascertained without my license. I looked at the officer for a moment strangely and before I could react he immediately barked, “give me your license or I’ll arrest you”. I pulled my license out and handed it to the officer reluctantly. He then asked me something, which I cannot remember exactly. The question was effectively asking why I hesitated to give him my license. The question seemed strange and obvious to me. I answered, “Have you not heard of the fourth amendment?” Obviously the officer was not happy with the answer because he put his hand on his gun, leaned in toward me and started barking at me “Your F*$%ing 4th amendment rights?! Say something again and I’ll arrest you!” The police officer went on and on for what seemed like an eternity but was likely shorter than I remember. I literally feared for my life. I was among a dozen or so “peace officers” and I feared for my life as a law-abiding citizen. For what? For answering the question that he asked. Granted, my response was in a tone that was not respectful, but it was not taunting or belligerent either. The situation was so bazaar to me that the question just seemed absurd. It would be like an officer pulling you over to ask you if you know how to drive. The obvious fact that he pulled you over would indicate your ability do drive. Therefore, you might likely respond, “Umm. Seriously?” That’s how I felt.

My dad at this point looked shocked too and we were both scared. The man was clearly out of control. I gazed at the other officers at the checkpoint. They all had a very confused look on their faces too. At this point, I was scared – not so much for me but for my dad. He has two bad knees and all I could imagine was the police pulling him from the car and slamming him to the ground – all because I answered his seemingly silly question.

I picked up my ‘mini computer’. I didn’t even care that it wasn’t recording. I just wanted to get the device out and visible. I figured the police, thinking they were possibly recorded might be enough to deter him from making an unwise decision. Worst case scenario – if I did manage to record anything that the recording might serve as evidence if anything “happened” to my dad and I. Apparently, this decision worked in my advantage. I didn’t even have to tell him the device was on or that I was recording. His actions ever so slightly changed from “Who’s your daddy now” to “just get the hell out of here.” He just handed my license back and started yelling, saying “Go ahead and say something again.” I kept my mouth shut and he said, “Just go”. So as I turned my gaze back toward the road ahead of me, I didn’t even inch forward a foot from the checkpoint before he started cussing at me and yelling. It was disturbing. This man has a gun — and is sanctioned to carry AND use one by the city. He was dangerous and frightening. This was only the beginning of a long night.

After making it through the stop, I pulled over and called 911. I told them what happened and they directed me to go to the police department in Beaver to file a report. My dad, knowing the area better than I do, advised that I go around the checkpoint a different way so I didn’t instigate that officer further. The 911 officer, still on the phone at this point, seemed to indicate that going the alternate route wasn’t a bad idea.

My dad and I drove to the Beaver police department the back way and got into town where I was greeted with a darkened police station. (see Google street view below)

I used the telephone outside the station to contact the police. The individual on the phone asked for my name, and said someone would be there shortly to take my report. My dad then said, “They aren’t going to be happy about you reporting one of their own.” I felt this was a slight risk, but was unlikely – something that only happens in movies. Boy was I wrong.

I went back to my truck for a minute and my dad stayed on the stoop of the police station. Just as I got into my truck, an officer pulled up. I got out of the vehicle and so did the officer. We met together and I began telling him what happened, my dad chiming in occasionally with his perspective and agreement that the officer was acting recklessly. The officer was very courteous and listened intently and seemingly concerned. He was a fairly young looking guy so I wondered if he was able to take the report or had to report to someone else first. The officer started to give me his perspective on the legality of sobriety checks and the reason for being able to side-step the 4th amendment (see the previously linked Wikipedia article for more information – essentially, it was decided that violation of constitutional rights is OK because its effective… hmm). I told him that at this point I wasn’t as concerned about that as I was with the officer’s very inappropriate actions and temper at the checkpoint. The officer may normally be OK. Maybe he had a bad day. Whatever the case, I didn’t think he needed to be at that station tonight. That said, I expressed my concern that all I wanted was to file the report and go home. Just as I did, another officer pulled up and started listening from his car. The second officer, also a young guy with a shaved head, stayed in his car for some time. After I while further into my story, the officer in the car told me “You know what, If I go and get that officer and he tells me it didn’t happen, I’m going to arrest you!” At that point, I told both officers that I was fine with that and I would prefer they got the officer so he could be present while I gave the report. I also told them that I might have been able to record the incident in question and really wanted to file my report. I could suddenly sense the mood change and the officer in the car looked visibly upset. Scared what may happen, I told the officer that I may have uploaded the recording already. I didn’t want them thinking that if they took the device, they could make it go away – and therefore the problem too.

The officer in the car said, “Go ahead and record me and put it on YouTube!” Based on his facial expression and the tone with which he said it, I thought he was being serious. I said “really?” “Yeah,” he said, “Put it up on YouTube. You’ll be arrested for wire fraud.” I then realized he was not serious at all. He was trying to threaten me. He got out of the car and kept saying, “go ahead and record me. But you can’t record anyone without their consent.” I said, “As far as I understand, you can record anything that is out in the public without consent. Reporters do it all the time. He said, “How much do you want to bet?” I said, “Well, nothing because unsanctioned gambling IS illegal, but I still contend recording in public is not.” At this point, I hadn’t even acknowledged that I HAD ACTUALLY recorded anything. I simply indicated that I might have been able to – but was uncertain yet. So I pulled the device out again and asked, “You did say I can record you then?” He said “No. I didn’t say that.” He changed his story — a flat-out lie. I asked him, “How can I even trust you to give you a report if you are already lying to me?”

At this point, another car pulled up and the bald-headed officer said, “There’s the chief of police right there! We can ask him!” I said, “Great, let’s go talk to him.” So I started walking toward the chief and the bald-headed officer started shouting, “Don’t say anything, he’s recording this whole thing!” I never affirmed or denied it to the captain or anyone. The captain then started concentrating on my device despite my request to file a report. He didn’t care about the report. He wanted that device away from me. He kept demanding it from me. “Give me that phone. I want to see if it’s recording.” “No!” I exclaimed. “I never said it was recording, HE did,” as I pointed at the bald officer. The captain said, “Well, give me the device, I want to see. You have turned something very simple into something very difficult.” I thought, why was it *me* making this difficult? I just wanted to file a report. They were the ones getting very interested in what devices I had and making the issue about me, rather than simply taking a report. Were citizens that used to rolling over and giving up their rights? Am I really the only person they’ve ever seen who has indicated they had rights? Do they really not care?

I simply held my device and occasionally looked at it. I was afraid at this point. I realized it was the Serriff’s office against my dad and me. The only defense I had was that the police had no idea what technological capability my device had. They also weren’t certain if I had uploaded a recording or streamed it somewhere that others could see. They weren’t certain if my device was a phone and I had someone listening/watching/reading to an open call/video feed/text-to-speech for an witness. That device felt like my only defense against what was increasingly looking like a completely corrupt police department. “Give me the phone,” the captain said assumingly. “No. See, if I WERE actually recording you, and it is actually against the law, I have a right to not turn that over to you and incriminate myself. That is the 5th amendment.” At this point, another few officers had shown up and had circled. There were 6 surrounding me. Other officers were now looking in the windows of my truck and running my license plates. They were just looking for a reason to arrest me. One of the additional officers on duty said, “You think because you read a few law books you know what’s going on? It’s called wire fraud in PA. You can record video, but you can’t record audio. I need to see what you are recording“, insisted the captain. The officers were drawing increasingly close, and had surrounded my dad and I. Some had their hands on their guns. Others were standing very threateningly – like a cobra ready to strike. OK, I’ve seen “Cops” and other shows. I see how these things go down. I was ready for someone to tackle me to the ground at any moment and arrest me. They would then “lose” my device to make sure there was no proof and then I’d be stuck on defense rather than offense. I was playing out every scenario in my head and I kept thinking my poor father was standing in harm’s way. I was still scared they would take him down hard and he just couldn’t handle that right now.

So after repeated attempts to take my device, the captain said, “OK, let’s go! We are done here.” I asked “What about my report?” And they just ignored me and got in their cars. They weren’t even going to take my report. My dad and I went back to our truck. The police stuck around for a minute until the realized I wasn’t going anywhere just yet. I made a phone call to 911 again and expressed my concern that we were going to be harassed or worse on our way out of town. This was a rather valid concern at this point because the police had ‘driven off’ but had circled back around. Despite their obvious attempts to hide – turning off their lights and creeping into position so I wouldn’t see them, I could see them placing themselves in strategic positions. The 911 dispatcher gave me the number for the state highway patrol. I called that number and was told that the officer would call me back. As I waited for a return call, the police officers repositioned themselves. One even threateningly put himself directly in the alley in front of me as if to say, “go ahead and pull out, I dare you.”

The state trooper on the line was very helpful by providing me with some information, but he was unable to come help me in what I perceived to be a dangerous situation. So, I hung up and put my phone down in the console. I knew there are anti-cellphone laws in the area, so I didn’t even want it in my hand where they could say I was on it. I pulled out and drove down toward Bridgewater. It was just a mile or so away to get out of Beaver’s jurisdiction in that direction. My dad and I ended up driving completely around the jurisdiction of Beaver police department out of fear.

I have never been afraid of anything like this in my life. I stand up when I feel it is necessary. When I was a child in school, Edmund Burke’s quote had a profound impact on my life: “all that is necessary for evil to triumph is for good men to do nothing.” I wasn’t grandstanding for my own amusement. I wasn’t trying to cause problems. I really just wanted to go home after watching a movie. However, this situation just got increasingly worse as more and more testosterone and abused power was added to the group. There was strength in numbers, but fortunately for me, there was also strength in using fear of the unknown and media scrutiny to keep me busy. I fully believe that if I had not had my device, or had the police had any certainty that I wasn’t recording them, I would have been in jail or dead — perhaps my dad too.

From our childhoods, we are told to cooperate with the police. However, I have always had distrust for law enforcement officers. Growing up, I was told about the police scandals in my little home town and knew that a badge isn’t necessarily a reason to trust someone. This certainly hasn’t helped the cause. Tonight I was threatened by an officer at a sobriety check point because I wasn’t familiar with them. I was directed into a bad situation by a 911 operator. I was threatened again by a gang from the police department – including the chief himself. I was told to give up my rights, that I had none. Even if I wanted to record the police officers, apparently it IS illegal to do so in PA (seriously, they can record you, but you can’t record them). I witnessed a police officer change his story to protect himself and others around him when he thought he was being recorded. The chief of police wouldn’t even take my report and in fact, threatened me instead of helping me. So the police are out to stop drunken driving (an admirable act), but were more than willing to break laws, abuse their power, and make threats to protect a man who was just as dangerous as a drunk driver – if not more so.

The police cry foul when citizens don’t help them out. Perhaps this is why. It has taken me three hours to write this up as my hands are still shaking and my heart is still literally racing from the experience. I still fear retaliation or reaction from them in some way. How are my dad and I to react?

Is Pennsylvania so corrupt that they give you means for the average citizen to defend themselves? What is a person to do if they feel their life is threatened and there is no other way to prevent harm other than to record the officer? What is a person to do when the police department is so corrupt that they won’t even take a report against one of their officers. I’m afraid to even go in to file the report now. I’m actually securing an attorney to handle the matter because I feel I have no choice. Had the police just taken my report, I would have been happier and there would have been no need for me to protect myself. Hell, they could have thrown the report away afterward. I wouldn’t have known any better. The point is, I didn’t make this a big deal. The police just gave me no choice but to make it one because they wanted to swing their authority around for absolutely no reason at all.

Please tell me what you think.

Update (May 9, 2009 – 9:34PM EST):

I’ve been doing some more reading and have found some more resources. First, I found the location to contact for public records. I will be requesting transcripts of the 911 calls, videos from the police vehicles, correspondence and public records about the officers involved last night. I also found that the Pennsylvania State Attorney General has a Public Corruption Unit. I will be contacting them on Monday to file a formal complaint and ask for an investigation.

Update (May 10, 2009 – 12:03AM EST):

In my previous version of this post, I posted that this was the Sheriff’s department. After doing some investigation and talking with my dad to confirm, it was the local Beaver, PA police, and not Beaver County police. Beaver is the county seat so the local police and Sherriff’s office are on the same street within blocks of each other. My sincerest apologies for the misunderstanding.

Update (May 10, 2009 – 1:00AM EST):
I was checking out Google Street view and found this ‘grab’ to be a bit humorous. That’s right, Google street view cams drove right by a speed trap on their way into Beaver from Bridgewater.

View Larger Map

IIS Security – Past and Present

This topic has been covered many times both by Microsoft and non-Microsoft employees. However, I’ve recently been asked what the main features of IIS 7 are and have seen a great deal of misinformation about IIS security on twitter, blog posts and forums.

I think, therefore, the issue deserves yet another look. In this post, I’m going to go over security in the past for IIS and then move on to talk about security features in IIS 7. These are not in any particular order. This post is not meant to diminish the many thoughtful works already created by others – both complimentary and critical. This is just meant to bring the subject back up for discussion again in hopes that you can be properly equipped with the decision making information you may need.

Ghosts of IIS Security Past

The reason for so much misinformation about the current state of security in IIS is likely due to the earned reputation the product had in versions previous to IIS 6.0. A quick search on the web for IIS 5 security vulnerabilities may be like a walk down memory lane for some of the more veteran administrators and IT staff across the globe. The search results are littered with critical vulnerabilities related to buffer overflows, ISAPI extensions, exploits on rarely-used features, or features that were available by a default installation. We are haunted by names like “Code Red” and “Nimda”. I don’t know about you, but those very names send shivers down my spine. I was consulting as a developer and web administrator for a very large property management company when these hit. We were lucky enough to avoid these as we had patched our services. That said, many whom I did business with on a regular basis were not very happy. So, to be clear, I feel the misinformation that is spread today is built on an element of experience with previous versions. Secunia reports 16 advisories and 6 vulnerabilities with IIS 5.  And so started the reputation , perhaps deservedly so, that IIS was not secure unless you really knew what you were doing with security.

Bill Gates was apparently visited by the ghosts of security past, present and future when he laid his head on his pillow January 14th, 2002. I say that because on January 15th, 2002 Mr. Gates sent out the now-famous trustworthy computing memo to every employee at Microsoft.  This set off a major revamp of products from the ground up. Standards were set for test planning and testing. Writing Secure Code was mandatory reading for every Microsoft developer and tester. The results have been staggering.

Security drastically improved in Microsoft products over the years, and IIS was definitely no exception to this. IIS 6 saw 5 security advisories and 4 vulnerabilities reported since 2003. Not to get ahead of myself, but IIS 7 has exactly 1 advisor and 1 vulnerability from Secunia. Compare this against Apache 2.0.x which has had 39 advisories and 23 vulnerabilities (4 of which are still unpatched as of this writing) and Apache 2.2.x which has had 10 advisories and 16 vulnerabilities (2 of which are still unpatched as of this writing) in the same period.  Now I have seen attempts ([1], [2]) to quantify or otherwise explain these numbers further. You can read those articles for yourself and determine how much weight you want to give them. However you skew it, the facts should speak for themselves – IIS has dramatically improved and taken a leadership roll in security in IIS 6 and 7. Our ghost of IIS past still haunts the product’s reputation today, despite obvious strides taken. Even if you feel you like Apache better I think it is only fair to give credit where it is due.

Improvements in IIS 6

The IIS team took the four tenants of Microsoft’s Trustworthy Computing initiative to heart: Secure by Design, Secure by Default, Secure in Deployment and Secure Communication. Since we are already on the next version, I won’t spend a great deal of time talking about the security improvements in the last version other than a brief overview so you know how they relate to changes in our current version, IIS 7.

IIS 6 took vast strides to improve security. During upgrade installations, IIS 6 was disabled by default if the previous server had not been secured by the IIS lockdown tool. The architecture was completely revamped to separate kernel-mode HTTP listening from user-mode application execution. Changes were made to application pools, authentication, access control, encryption and certificate handling, auditing, logging and patch management that made the product far superior to its predecessors. You can find a detailed list of these features on TechNet.  SecurityFocus did a comparison of these features in March of 2004.Server Watch wrote an article in December of 2003. By most accounts, everything accomplished in IIS 6 was a huge step in the right direction.

Despite the massive steps already taken in IIS6, IIS 7 took these all a bit further. Let’s go ahead and investigate these now.

Improvements in IIS 7.x

Customizable Installation

Continuing with the tenant of being secure in deployment, IIS 7 has made installation a wonder to behold. In IIS 6, you could reduce your attack surface by disabling features native to web server. However, these features were still loaded into the process. This carried not only a security factor, but also a performance and memory footprint issue.  IIS 7 has a completely modular architecture. That means that features which you do not want are not only NOT loaded into the process, you can leave the bits for those features off of your disk completely.

Limitable Attack Surface

This is a bit dubious and is essentially part of the customizable installation. By reducing the modules that are available on disk or loaded into a process, you significantly reduce the attack surface for your specialized web servers. If all you intend to do is serve static content with caching and no default documents, you can simply install the static file handler and caching module and leave the rest of the IIS modules off of your server. Additional controls and limitations will also reduce your attack surface and I’ll cover those below.

IUSR account

Anyone who has tried to migrate an IIS installation from one machine to another or attempted to recover your installation on a new machine, previous to IIS 7, has likely run into an issue with the local “IUSR_” account.  IIS 7 now uses a built-in IUSR account that allows you to easily copy your security settings from one machine to the next. This is great news for those using distributed configuration in web farms, recovery, restoration, or replication.

IIS_IUSRS group

IIS 6 introduced the IIS_WPG group. Application pool security identities had to be assigned to this group in order to host the w3wp.exe process. Like the IUSR account, IIS 7 now creates a built-in security group (IIS_IUSRS) and assigns application pool identities to the group automatically. You can find more information about the built-in user and built-in group for IIS 7 on IIS.NET (Understanding the Built-In User and Group Accounts in IIS 7.0).

ASP.NET / IIS Unified Security Architecture

Previous versions of IIS did not provide a unified approach to security with ASP.NET. The IIS 7 unified request pipeline that supports both Windows and non-Windows principals and provides one place to do all authentication and authorization. Apart from simplification and performance improvements, this also reduces the attack surface and allows for greater flexibility in authentication / authorization scenarios with custom modules.

Request Filtering / URL Rewriting

IIS 7.0 includes a request filtering module that is based on the URLScan ISAPI Filter for IIS 6.0. The module helps you tighten security of your Web servers.

The IIS team has also released an add-on URL rewrite module for IIS 7.0, which provides functionality for rule-based URL manipulation. Even though the primary purpose of the URL rewrite module is to rewrite URL paths for requests, the rewrite module can also be used as a security enforcement tool that helps prevent access to Web site content.

Application Pool Identities

On top of Application Pool Isolation, IIS introduces a new security feature in Service Pack 2 of Windows Server 2008 and Windows Vista. It’s called Application Pool Identities. Application Pool Identities allows you to run Application Pools under an unique account without having to create and manage domain or local accounts. The name of the Application Pool account corresponds to the name of the Application Pool.

Kernel mode SSL

The implementation of SSL has changed from IIS 6.0 to IIS 7.0.  On Windows Server 2003, all SSL configuration was stored in the IIS metabase and encryption/decryption happened in user mode (required a lot of kernel/user mode transitions).  On Windows Vista and Windows Server® 2008, HTTP.sys handles SSL encryption/decryption in kernel mode, resulting in up to 20% better performance for secure connections. 

Configuration Improvements

IIS 7.0 allows locking and unlocking configuration settings in various levels and scopes. Locking down configuration means that it cannot be overridden (or set at all) at lower levels in the hierarchy. Unlocking configuration can only be done at the level where it was locked. This is useful, for example, when creating different configuration for different sites or paths, and only some of sites and paths are allowed to override it. Locking can be done at the section level or for specific elements, attributes, collection elements and collection directives within sections.

Dynamic IP Restriction

IIS 7 provides a new module that allows dynamic, temporary IP address restriction. This module prevents brute force attacks and HTTP clients that make unusually high number of concurrent requests or a large number of requests over a short period of time.

Summary

A verbose list of security features in IIS 6 and IIS 7 might be nearly impossible. Apart from the obvious features, there were numerous improvements to code made over these two versions that make the product far more secure than IIS 5 and earlier. That said, this should give you a summary start on information. I’ve listed some reference documents that may help you understand these features better.  In general, I would encourage you to ask questions of the product team and or other users on the IIS.NET forums if you hear something that sounds negative regarding IIS. If the feedback is true, the product team has the benefit of improving the next release. If the feedback is unfounded, the product team has the benefit of helping you find the information you need to make an informed decision.

See Also

Philly Code Camp 2009.1

I flew to Philadelphia from my home in Pittsburgh to attend and speak at the first Philadelphia area code camp for 2009.

I spoke on Extending IIS 7. You can find my photos of the event on flickr.

I took the opportunity to visit family that I hadn’t seen in ages and to see Philadelphia — a big deal for me as I’m a history buff.

I might be Speaking at CodeStock

OK, so I had intended to announce that I posted a session submission to CodeStock and that voting was open. However, I procrastinated and Shawn Wildermuth beat me to the punch. So in an act of utter creepiness, I am modeling my post after his and invoking his name for extra copy-cat points.

For those of you that don’t know what CodeStock is, think of it as a CodeCamp done better – in two days instead of one. In their own words:

CodeStock is about Community. For Developers, by Developers (with love for SysAdmins and DBAs too!). Last year and idea started at CodeStock to mix Open Spaces within a traditional conference. This year we’re going to crank things up to 11 and rip off the knob – and you’re being drafted to help.

This two-day conference, of sorts, will be kicked off June 26th and costs only $25 to register.

My sessions are in the running, right along side Shawn’s. As he so eloquently pointed out, CodeStock attendees get to pick what sessions they wish to see from all of those submitted by would-be speakers. If my session doesn’t get picked, perhaps I can just watch Shawn. I’m told he has given a presentation or two in his career 🙂

So if you haven’t already, please go register for CodeStock so you can vote on those sessions while you can! Session voting ends on May 15th.

(Thanks, Shawn!)

Installing CakePHP on IIS 7

Recently I spoke with someone on Twitter who was having issues running CakePHP on IIS. With all the talk about ASP.NET MVC on IIS, folks forget that the MVC pattern works in other languages as well. CakePHP provides MVC  development on PHP. That said, I wanted to dive in and see what the issues were involved in getting this project up and running on IIS 7. I managed to get it installed pretty quickly, but it does take a little tweaking to get you up and running. I’ve chronicled my adventures with CakePHP below in case anyone else is having issues. That said, I must first say that I am not an expert working with CakePHP. This was my first experience with the project, so this information is provided “as-is” and should be taken with a grain of salt. With this demo, I’ll be walking through the “Cake Blog Tutorial” offered on cakephp.org, and modifying it as needed to work with IIS 7. That said, let’s get started.

Prerequisites

Yes, there ARE a lot of Prerequisites, but these are pretty typical for any MVC app on any platform.

Assumptions / Conventions

For the purposes of this post, I will use the convention/assumption that you have unzipped CakePHP to c:inetpubCakePHP . You should have the following paths now:

  • c:inetpubCakePHP
    • app
    • cake
    • vendors
    • .htaccess
    • index.php
    • version.txt

I will also use the assumption that this is being installed on the “Default Web Site”. This is unlikely what you are doing, so you’ll want to replace the “Default Web Site” instances in the steps below with your site or application path.

Lastly, I will assume that you are using and have already installed MySQL. You may use another database if you please, but this blog will reference MySQL.

Installing the Blog Sample

Pointing IIS to the cake document root

First, you’ll need to configure your website to point to the correct location. Using the assumptions above, the correct location would be c:inetpubCakePHPappwebroot .

Creating a Blog Database

Second, configure your database connection. To do this, you’ll need to create a blog database, and then point your configuration to that new catalog.

Start by creating a new MySQL Catalog using your favorite tool. I used MySQL Administrator. Simply right click in the catalogs and click “create new schema.”

Create a schema named “CakeBlog”. Once the schema is created, click on the “Tools” menu and select “MySQL Query Browser” and execute the following script:

/* First, create our posts table: */
CREATE TABLE posts (
     id INT UNSIGNED AUTO_INCREMENT PRIMARY KEY,
     title VARCHAR(50),
     body TEXT,
     created DATETIME DEFAULT NOT NULL,
     modified DATETIME DEFAULT NOT NULL8.);

/* Then insert some posts for testing: */
INSERT INTO posts (title,body,created)
      VALUES ('The title',
                  'This is the post body.', NOW());
INSERT INTO posts (title,body,created)
      VALUES ('A title once again',
                  'And the post body follows.', NOW());
INSERT INTO posts (title,body,created)
      VALUES ('Title strikes back',
                  'This is really exciting! Not.', NOW());

* This SQL code copied verbatim from tutorial found here:

You’ve now created your database and a blog posts table with some default posts. Time to configure CakePHP to read from the database:

Cake Database Configuration

We’ll need to let CakePHP know where the database is. Copy database.php.default in c:inetpubCakePHPappconfig to database.php

Open c:inetpubcakephpappconfigdatabase.php and change the $default variable to point to your database:

var $default = array( 'driver'    => 'mysql',
                      'connect'   => 'mysql_connect',
                      'host'      => 'localhost',
                      'login'     => 'CakeBlog',
                      'password'  => 'c4ke-1z-k00l',
                      'database'  => 'CakeBlog',
                      'prefix'    => '' );

* This PHP code copied nearly verbatim from tutorial found here:
http://book.cakephp.org/view/326/The-Cake-Blog-Tutorial

You should now be able to open your browser to your application and see the default cake configuration page.

Setting up Rewriting Rules

CakePHP uses mod_rewrite, but also provides the ability to use Cake’s built-in ‘pretty URLs’. We’ll be importing the mod_rewrite rules from the .htaccess files from the default cakephp installation into the IIS URL Rewrite module. We’ll then have to modify those rules.

Start this process by opening the IIS Management Console. Open your application path. In this instance, we are using “Default Web Site”.

  1. Click on the “Default Web Site
  2. Open the “URL Rewrite” module
  3. Click on “Import Rules…” in the Actions pane
  4. Click the “” button next to the “Configuration file” textbox.
  5. Select the c:inetpubcakephp.htaccess file and click “OK
  6. Click the “Import” button
  7. Click the “Apply” button in the “Actions” pane
  8. Repeat steps 4, 5, 6 and 7 for c:inetpubcakephpapp.htaccess and c:inetpubcakephpappwebroot.htaccess files.

The rules are imported, but now you’ll need to edit the rules.

  1. Click the “Back to Rules” button in the “Actions” pane
  2. Edit the two rules with the action starting with “webroot/
  3. Remove the “webroot” portion of the “Rewrite URL”. Your paths should now look as follows:

Creating your MVC Application

The remainder of your application setup should follow the steps found in the original “Cake Blog Tutorial”. There is nothing different between IIS and Apache at this point, so copying the steps would be a bit redundant. Start with the step named “Create a Post Model”. Much like ASP.NET MVC, Cake provides an MVC pattern for developing PHP applications.

Once you have completed the steps, you should have a default site that looks something like the following:

Summary

Installing CakePHP on IIS is actually not much different from installing on Apache. The main difference lies in the implementation of mod_rewrite on Apache vs URL Rewriter in IIS. Obviously the installation of PHP differs from Apache. IIS makes the installation of PHP simple with Web Application Installer. If you are using CakePHP on IIS, I would be interested to hear if your experience was different than mine.

Charlotte Code Camp – Spring 2009

I flew to Charlotte from my home near Pittsburgh to attend the spring code camp this year.

When I arrived I found out that a Pete Mourfield was not going to make it in time to give one of his presentations. Brian Hitney suggested that I do a presentation at the last minute to fill in. I took the dare and agreed to do a presentation on MGrammar — something I had been checking out for about a week. I had about 50 minutes to prepare. In that time I downloaded the Oslo bits over the slow wifi at the school and installed them on my laptop. I had no slide deck and I had very little idea of how I would procede.

I managed to give a fairly fun presentation and got some great reviews in the process.

You can find some photos of the event on flickr.

A matter of pixels

I’ve been sick a lot lately. In fact, in my entirely life, I don’t ever remember being this sick for this long. It’s been weeks with the same cold – months if you consider the on-again/off-again problems I’ve been having. I guess it could be my fault. I’ve never been a big fan of drugs or doctors.

During my sick time, I try to do some work and often find myself barely able to concentrate. You know how it is, your head feels like its floating, and then you cough or sneeze and you feel as though your body has shaken apart into a million pieces. I’ve always equated that feeling with the visualization of my head becoming pixilated or snowy. That brings me, ever so strangely, to my current topic.

It’s been years since I focused on the front of web development issues. Back in the late 1990’s and early 2000’s I tinkered with client-side web development a great deal. I was writing “Ajax” applications before they were known as that. Of course, they all ran on intranet sites for my clients because they would only work in IE. I learned something back then. It was all a matter of pixels. In many cases, you had to take a box model and calculate precisely where things were and how they should line up. Of course, back then I was still using tables for layouts and cutting up images into manageable slices to put in individual or spanned table cells. Making those images line up, then, was extremely important to work on all browsers.

Over the years, I drifted away from client-side development. I have been concentrating on the back end of the web development stack. IIS, Apache, SQL Server, MySQL, MSMQ, MQ Series, BizTalk, WF, Remoting=>WCF, and associated technologies have been where I spent my time. What happened with data once my server pieces were done was beyond me. As a 3-year veteran working with IIS at Microsoft, you can see why this is important to me. That said, to help make IIS a better web server, it is always useful to actually know what is being served by your webserver, and why it may be important to you. I started playing with ASP.NET MVC which of course means I had to look at the “View” side of things again. To get a better grip on ASP.NET MVC, I decided to implement my blog in Oxite. Oxite isn’t a product, its a technology sample that is being followed to its logical conclusion – full implementation. This project fills the void of most samples by truly evangelizing the technology in a real-world implementation that can (and should) be implemented by others. Many of the samples out there are great examples of how to start an app, but never demonstrate that you can fully implement your project in the technology.

So, as I decided to dive in again and start playing with client-side development, I realized quickly that I needed to relearn everything I once knew. Box models were still important, but so was understanding the nuances of where my pixels within the context of their containers. Unlike with tables, that are fairly predictable, I learned very quickly that CSS-based DIV layouts can break down quickly if you aren’t using the proper attributes in your styles. div wrapping, overflow, z-indexes, display styles all became important topics for me to learn. I was trying to learn All this while I was laying sick in my bed!

I must say that I’m hooked now. I love technologies like jQuery. I’ve written a few plug-ins already. Some of them you see on this site, others will be on my site soon. Some will be coming in next revisions and available for download from this site. You can get the twitter client plug-in that scrolls at the top of this site’s page by downloading the Oxite skin on this website. I love that the community has developed many resources such as Yahoo’s CSS reset and associated style sheets.

Don’t get me wrong, I’m not an expert in these technologies overnight. I’ve got a LOT to learn. But I just keep telling myself, its all a matter of pixels. Count them out and everything will turn out ok!

Some resources for your own journey in client-side design/development:

  • jQuery – jQuery is a technology rooted in Microsoft’s leading XmlHttpRequest object. jQuery native core allows you to assign behavior to elements of the document object, perform common tasks such as layout, animations, fades and much more. This site’s plug-in repository is worth checking out and scouring for examples.
  • jQueryUI – If you like jQuery, this framework of UI plug-ins will help you get a clean, professional look for any website. The site allows you to create a customized theme, download it, and apply it to your layout. Absolutely brilliant.
  • YUI – Yahoo User Interface Library provides many user interface modules. I highly recommend the reset CSS. It helps all browser get on the same footing as far as padding, margin, borders, and spacing go. Very useful tool to help you achieve your desired look/feel on all browsers.
  • The Ajaxian – Great blog with useful information about developing dynamic content on the client side.
  • Introducing JSON – A good starting spot to learn about JSON (JavaScript Object Notation) and associated extensions such as JSONP. JSON allows you to serialize objects across Ajax requests. jQuery provides support for JSON/JSONP.
  • Microsoft: Introduction to JSON in JavaScript and .NET – Useful information to further your understanding of JSON.
  • HTML 5 Draft Recommendation – It always helps to know where your rendering specification is heading. HTML 5 supports things such as canvases that can render objects of irregular shapes and even manipulate individual pixels.
  • Common layouts – This useful site provides the code needed to produce common layouts in fixed and fluid mode.
  • Firebug – This tool is useful if you need to inspect a website’s output and determine what isn’t working. Often times it is hard to tell what setting is making our layout go wildly wrong. Firebug allows you to view the aggregate of your CSS calls for a given element, and let you see where your settings are coming from. The tool is invaluable to any client-side developer.
  • FireUnit – Provides JavaScript debugging. This is a necessary tool for anyone developing modern, dynamic, and interactive web UI today.
  • Color Schemer – This site provides a great tool to create color pallets for your site.

 

There is so much more to look at that I’m leaving out here. Obviously I could make the list extremely long. However, emphasizing everything means I am emphasizing nothing. I suggest those sites above as a good starting point.

Happy Coding!

IIS cannot start after upgrade to Vista SP1

Some time ago, I tried to start up the IIS Management Console on my Vista machine and I received an exception. After trying a few quick fixes, I gave up. I had several VPC images that I worked from and I didn’t particularly need this machine to work when I had so many others.  However, I’ve been doing a great deal of development on this machine now, and having IIS working is obviously rather handy. So, I tracked down the exception and solved my problem. I thought I’d go ahead and chronical my adventures for anyone else who is having this issue and needs help.

So first of all, the error that was displayed when I started inetmgr was as follows:

---------------------------
Failed to connect
---------------------------
There was an error when trying to connect. Do you want to retype your credentials and try again?
Details:
Creating an instance of the COM component with CLSID {2B72133B-3F5B-4602-8952-803546CE3344}
from the IClassFactory failed due to the following error: 8007000d.
---------------------------
Yes   No
---------------------------

So I thought that this might be a configuration error. I tried to roll back to a known good configuration but appcmd failed with the following exception:

ERROR ( hresult:80070426, message:Command execution failed.
The service has not been started. )

I tried to start the service with a good old fashion iisreset command and the following exception occurred:

Attempting stop…
Internet services successfully stopped
Attempting start…
Restart attempt failed.
The IIS Admin Service or the World Wide Web Publishing Service, or a service dep
endent on them failed to start.  The service, or dependent services, may had an
error during its startup or may be disabled.

Once again, I thought I’d go into the services console and try to start IIS manually. After trying to start it manually, it failed, stating that a dependent service failed. So I looked at Windows Process Activation Services (WAS) and noticed it was stopped. I tried to start it manually and found the following:

—————————
Services
—————————
Windows could not start the Windows Process Activation Service service on Local Computer.
Error 13:
The data is invalid.
—————————
OK �
—————————

So I checked out the event log and found the following four entries:

First Event :

Log Name:      System
Source:        Service Control Manager
Date:          9/21/2008 11:52:00 PM
Event ID:      7001
Task Category: None
Level:         Error
Keywords:      Classic
User:          N/A
Description:
The World Wide Web Publishing Service service depends on the Windows Process Activation Service service which failed to start because of the following error:
The data is invalid.

Second Event:

Log Name:      System
Source:        Service Control Manager
Date:          9/21/2008 11:52:00 PM
Event ID:      7023
Task Category: None
Level:         Error
Keywords:      Classic
User:          N/A
Description:
The Windows Process Activation Service service terminated with the following error:
The data is invalid.

Third Event:

Log Name:      System
Source:        Microsoft-Windows-WAS
Date:          9/21/2008 11:51:59 PM
Event ID:      5005
Task Category: None
Level:         Error
Keywords:      Classic
User:          N/A
Description:
Windows Process Activation Service (WAS) is stopping because it encountered an error. The data field contains the error number.

Fourt Event:

Log Name:      System
Source:        Microsoft-Windows-WAS
Date:          9/21/2008 11:51:59 PM
Event ID:      5036
Task Category: None
Level:         Error
Keywords:      Classic
User:          N/A
Description:
The configuration manager for Windows Process Activation Service (WAS) did not initialize. The data field contains the error number.

I checked through my event logs and realized that this started happening after I had upgraded to SP1. I hadn’t recognized this as the issue because, as I said, don’t typically use IIS on this machine on a regular basis. I decided to go back to my initial assessment that this had to be configuration related. I started doing comparisons between configuration of a pure Vista installation vs a Vista machine with SP1. I found that the schema had changed during the install, but something had been left out.  The schema file was updated to add the configurationHistory configuration section, but a corresponding section definition was not added to the applicationHost.config file.  

Whether this was what was causing the problem or not, I knew this was going to cause a problem. I added the following configuration entry to the applicationHost.config file under the section group for “system.applicationHost”. 

<section name="configHistory" allowDefinition="AppHostOnly" overrideModeDefault="Deny" />

After this I started the WAS service, the World Wide Publishing Service and the IIS Admin Service. I opened up the IIS Management Console and everything was working just fine.

I’m not sure what exactly happened during the SP1 upgrade that caused this file to not be updated, but I’m pleased to report that all things are up and running again.

Enabling VS.NET 2008 to work with IIS 7.0

This is likely old ground for some, but I thought I’d cover it again just in case. As you may know Visual Studio allows you to create a new web site on IIS. However, there are some minor steps that you need to complete before it will work appropriately.

Let’s walk through this.

  1. Open Visual Studio .NET 2008
  2. Go to File | Web Site…
  3. Click the Browse… button to choose a Location
    1 - vs08-newwebsite-sm
  4. Click on the Local IIS button on the left
    2 - vs08-iis-sm
    You’ll notice the IIS 6 Metabase and IIS Configuration Compatibility need to be
    installed as well as ASP.NET. The next steps we’ll go through will enable this for
    you.
  5. Go to Start | Control Panel and click on the
    Programs and Features
    applet
  6. Click on the Turn Windows features on or off button on the left
  7. From the Windows Features window, select the IIS Metabase
    and IIS 6 configuration compatibility
    option under IIS 6 Management
    Compatibility
    as well as ASP.NET under Application
    Development Features

    3 - vs08-features-sm
  8. Click OK and wait as Windows configures the service
    4 - vs08-configuring
  9. Once Windows is done configuring IIS, it may ask you to restart. Click Restart
    Now
    .
    5 - vs08-restart
  10. After rebooting, you should be able to walk through steps 1-4 again and create a
    Web site with the Local IIS option.
    6 - vs08-working-sm

This should be all you need to do to enable Local IIS integration with VS.NET 2008.

IIS 7.0 Error Support

I know that most of you reading the blogs on this site have already seen how handy the errors are in IIS 7.0 as compared to previous error conditions. This weekend, I was playing with BlogEngine.NET and thought I’d put it on my personal site (tobint.com) to try it out. I downloaded the software and tried setting it up on my server. After following the brief instructions, I hit an error:

HTTP Error 500.22 – Internal Server Error
An ASP.NET setting has been detected that does not apply in Integrated managed pipeline mode.

In previous versions of IIS, this might have been all that I had to go on. I’d then search one or several search engines for that exact error and read through blog posts, forums, knowledge base articles and FAQ’s before I found what I needed. In IIS 7.0, I found the friendly error page awaiting me:

Error 500.22

 I looked at the “Things you can try” and a picked the first “fix” on the list. Since my application was not in the Default Web Site, I ran the appcmd for my application in “tobint.com/”. 

AppCmd

 As you can see, the error page correctly identified that my configuration needed to be migrated, and gave me the steps I needed to migrate it effectively. No searching the web. No trying to trace the problem down. No turning on tracing for ASP.NET pages. 

I love this feature. It’s a huge time saver and I don’t think it gets bragged on enough.