Greetings all,

Thanks for the great responses so far. One thing I did forget to mention is the fact that the Web service in question is actually the second we've done for this particular contact within GRWBSC, and it's the fourth we've done for the particular group/team within GRWBSC. All four projects were on LAMP technology, and we were very up front about that on our first contract. No one seemed to care until someone high up got word and got ticked.

I think this makes a world of difference when it comes to delivering something that the client wanted. Who is my client's client exactly? Is it the project lead, the team or group, or GRWBSC as a whole company? As far as my client is concerned, it's the project group/team since the makeup of GRWBSC is very "team vs team".

Regardless, my client via me provided exactly what was requested of us, both in what was requested for the service and what was requested about the NetCraft "fix." If GRWBSC or anyone therein is unhappy with the results, then it can only be because they were not specific.

I feel some responsibility for building the HTTP header spoof since it "feels" like I'm misleading my client's client. However, I don't feel any responsibility for building a Perl solution, even when an ASP one may have been prefered, since any such preference was in no way specified by anyone.

gryphon
code('Perl') || die;