Hi! I am Chris, and this is my blog. This is blog is about, well, just about everything that I want to post about. So here’s a little about me …
I the “Web Guy” at Edinboro University of PA. At Edinboro I basically have 2 major focuses:
Edinboro’s Public Website is driven by a content management called DotCMS. My job here is make sure that the rest of the University is able to contribute to the website effeciently. From coding, to designing, to support and training there is a lot to do there.
Edinboro’s Portal is delivered by Oracle Application Server 10g Portal. There’s a mouthfull. Here I install, configure, and develop portlets as well as design, and …
I also do work on serveral other sites in my spare time includeing my Church, Grace. We just went live with the new site based on the content management system Expression Engine. We just recently released a new website, ServErie, which will also be a work in progress for some time.
Other than web development, I am a gamer. I am currently playing a little game called Warhammer Online Age of Reconing (WAR). I also play keyboard and piano at my church. I have a wife and an awesome 1 yr old.
So now you know who I am and what I do. I must warn you however; though I may be an Edinboro University Employee, this blog constists of my own personal thoughts and is in no way intended to represent those of Edinboro University of PA.
Now with that out of the way, enjoy my blog.
Posting tweet...
Powered by Twitter Tools
2 comments ↓
Hi Chris,
Apparently we are having trouble with your trim plugin. We only installed it on dev to test, but it seems to be changing the response header. Here is the jira that my colleague Casey entered:
We took a snapshot of prod + db yesterday and rebuilt dev with it. We have a page with some JS on it that eats some XML coming out of an ajax.dot. We accomplish this with $response.setHeader(”Content-type”, “text/xml”). Works great. This same code in to dev comes back with the HTTP response header’s showing: “Content-Type text/html;charset=UTF-8″. The problem we’re having is that the JS won’t eat the return unless we have the appropriate XML HTTP response header. What do we need to change to make that happen?
We removed it and now it works ok.
Thanks for the report Brad. I don’t know when or if I will have time to look at this. Funny thing is, I know I have used $response.setHeader() to set other content types (i.e. the iCal Feed thing). My guess is it would have something to do with the where the filter ends up in the web.xml. If you find anything else out, please let me know.
Leave a Comment