Not at all. The lack of a content-type header is a likely culprit for the symptoms you reported, so I asked. Putting the content-type header (and any other necessary headers) in the template gives a more cohesive solution than putting the content-type into code and the content into a separate template. On the other hand, emitting a content-header early, from code, makes a number of problems easier to diagnose.