Ah, mod-perl{{{ shudder }}}.
"$asperl->setContentType($apache->content_type());"
I think there's a bunch of relevant code we're not seeing. Without having been
set prior, I don't believe $apache->content_type will return the right header
in this situation because it relies on file extensio
> >
> >>>-Original Message-
> >>>From: Gunnar Hjalmarsson [mailto:nore...@gunnar.cc]
> >>>Sent: Thursday, July 02, 2009 1:24 PM
> >>>To: beginners-cgi@perl.org
> >>>Subject: Re: content type headers
> >>>
> >>&
ageid=123456&size=800x600
the HTTP response headers would probably shed the most light on the problem,
nudge, nudge;-)
>>-Original Message-
>>From: Gunnar Hjalmarsson [mailto:nore...@gunnar.cc]
>>Sent: Thursday, July 02, 2009 1:24 PM
>>To: beginners-cgi@perl
Hellman, Matthew wrote:
The answer to your problem seems to be making sure one and only one
content-type header is returned with the image, and that it has the
correct value (e.g. Content-Type: image/jpeg or whatever).
Right, and it just struck me that this is probably a web server
configurat
>>Hi,
>>
>>I've got some old code to deal with and I have hit a problem.
>>
>>If there is a request for a page that has mixed content EG: 'text/html'
>>and 'image/jpeg', the image media is not being displayed correctly under
>>the FireFox browser.
>>
>>The way things currently work is that media ot
Dermot Paikkos wrote:
If there is a request for a page that has mixed content EG: 'text/html'
and 'image/jpeg', the image media is not being displayed correctly under
the FireFox browser.
What exactly do you mean by that? When you use a browser to request a
usual HTML page with IMG elements,
