Thanks again. What I am working with here is a well established project with 1000s of lines of code on release number 43; maybe I am showing too much faith, but I just don't think they're suddenly forgotten that they need to send properly formatted HTTP headers. The code to do so is in there somewhere, I just can't find it. And somehow, someway, something is getting mangled and IE interprets that as special characters, and I posted here to see if anyone had ever seen something similar.
The image problem is just a symptom of the headers issue; if I can find the header code and see why it's spouting our special characters, then the image problem will go away (I am sure). Thanks again for your help, it's been useful Mick -----Original Message----- From: Clinton Gormley [mailto:[EMAIL PROTECTED] Sent: 16 April 2007 12:06 To: michael watson (IAH-C) Cc: Clinton Gormley; modperl Subject: RE: Malformed header from script On Mon, 2007-04-16 at 11:49 +0100, michael watson (IAH-C) wrote: > Hi > > Thanks for all your help. If I print out the header line myself, before > anything else is printed out, then for some reason none of the images > are produced. Images are produced dynamically using perl and GD. If I > leave everything alone, I get images that work properly but no HTTP > header; If I hack away and print the HTTP header myself, then the > header looks fine but my images don't get produced (it's not that the > URLs are wrong, the img-tmp/ directory remains empty). > > I don't pretend to understand this, nor do I expect you to, needless to > say it's not as easy as just printing the headers myself. OK - first, I think that the missing header was definitely the issue that you originally talked about. The second problem of the images not being produced is trickier. Is the request dieing before it produces the images? I can't help you here - more debugging statements required. You may want to read here for more about outputting headers from registry scripts: http://perl.apache.org/docs/2.0/user/coding/coding.html#Generating_HTTP_ Response_Headers Other than that, without more code, I don't think we can help you. hth clint > > Finally, thanks for the tip RE 'PerlOptions +ParseHeader'; it made > little difference, but at least now that part of the code is correct. > > Thanks again > > Mick >
