Mailing-List: contact users-help@httpd.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@httpd.apache.org
Received-SPF: pass (athena.apache.org: domain of aw@ice-sa.com designates
 212.85.38.228 as permitted sender)
Message-ID: <4AF09144.6080504@ice-sa.com>
Date: Tue, 03 Nov 2009 21:23:32 +0100
From: =?ISO-8859-1?Q?Andr=E9_Warnier?= <aw@ice-sa.com>
Reply-To: users@httpd.apache.org
User-Agent: Thunderbird 2.0.0.23 (Windows/20090812)
MIME-Version: 1.0
To: users@httpd.apache.org
References: <6a5aad1a0911031120n44e0f1a7r66daea6157024f91@mail.gmail.com>
	 <20091103202610.63f2bdc7.rambo@id.uw.edu.pl>
	 <4df3a1330911031132m6aa8c896pa01223811b537a49@mail.gmail.com>
 <6a5aad1a0911031206xe2d72f2k777aa143228f7161@mail.gmail.com>
In-Reply-To: <6a5aad1a0911031206xe2d72f2k777aa143228f7161@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [users@httpd] pdf report generation - content type text/html

b k wrote:
> Thanks!! Actually, it's a java based app on the WebSphere app server that
> sends the response to Apache web server which in turn sends the response to
> the browser. I tested the reports directly on the App server which are
> working fine. I suspect something is wrong in the apache config. I also
> checked mime.types file which includes pdf entry.

Apache will only generate itself the "Content-Type" and 
"Content-Disposition" response headers, if the file being served is a 
file that Apache itself picks up from the filesystem.  That is also when 
it uses the mime.types file (to try and guess the type).

When it is an application which generates this data (or file), then it 
is the responsibility of the application to add these 2 headers to the 
response (at least the Content-Type).
When Apache sees a response about to go out, without a Content-Type 
header, it will add one of it's own, but that is a default set in the 
configuration, usually set to
Content-Type: text/html
(because that is the most likely on a webserver)

So, whatever your application is, it is probably not producing this or 
these HTTP headers, which is why Apache adds its own default 'text/html' 
header, and that is the reason for the problem.

To my knowledge, there is nothing in Apache that will remove a 
Content-Type header set by an application and replace it by another one, 
unless you have specifically configured it to do that.

There are additional miseries in this due to the inconsistency of IE 
versions in interpreting the content coming from a webserver, but I 
believe that would be a second step, and you need to resolve the one 
above first.

---------------------------------------------------------------------
The official User-To-User support forum of the Apache HTTP Server Project.
See <URL:http://httpd.apache.org/userslist.html> for more info.
To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
   "   from the digest: users-digest-unsubscribe@httpd.apache.org
For additional commands, e-mail: users-help@httpd.apache.org