Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

Raw HTML on browser - Http Server Serving wrong MIME type

14 views
Skip to first unread message

debashi...@target.com

unread,
Sep 25, 2009, 2:31:40 PM9/25/09
to
Hi,

We are having an issue of raw HTML(JSP) code being displayed on browser. This is an intermittent behaviour and seems to occur under high load.
In our project, the JSP pages reside in the Application Server(IBM websphere on UNIX environment and the web project runs on ATG framework).
Traffic is routed to the application server via the IBM HTTP Web servers i.e. the webservers are the first to intercept the incoming http requests.
We have tried to debug the issue and found that the response headers have different MIME type when the browser displays raw HTML code.
Somehow it is being set to text/plain instead of text/html.

Here are the response headers:

Good response:

Date: Fri, 25 Sep 2009 04:53:22 GMT
Server: IBM_HTTP_Server
Content-Length: 15012
X-ATG-Version: UNKNOWN [ DPSLicense/0 ]
Keep-Alive: timeout=15, max=92
Connection: Keep-Alive
Content-Type: text/html;charset=UTF-8
Content-Language: en-US

Bad Response:

Date: Fri, 25 Sep 2009 04:52:39 GMT
Server: IBM_HTTP_Server
Content-Length: 15017
Keep-Alive: timeout=15, max=98
Connection: Keep-Alive
Content-Type: text/plain
Content-Language: en-US

We are setting the MIME type in the JSPs too like


Please let me know if anyone has faced this issue and can help me debug it.
Is it somethinng to do with the webserver setting wrong MIME type under load?
If so please let me know where to look at to fix it. Thanks!

Regards,
Debashis

Eric Covener

unread,
Oct 2, 2009, 5:54:09 AM10/2/09
to
debashi...@target.com wrote:

> Content-Type: text/plain
> Content-Language: en-US

Likely there's a path through your JSP/servlet where no Content-Type is
set. IHS default conf has DefaultType text/plain which can safely be
removed which would at least let your browser guess instead.

--
Eric Covener

brent.halsey

unread,
Nov 5, 2009, 2:26:18 PM11/5/09
to
We are also having this issue. Any idea how to fix this?

brent.halsey

unread,
Nov 5, 2009, 2:57:28 PM11/5/09
to
Nevermind- resolved the issue by updating the httpd.conf and setting the Default_Type to text/html instead of text/plain. Thanks!
0 new messages