httpd-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Joshua Slive" <>
Subject Re: [users@httpd] XML/XLS filtering
Date Thu, 14 Feb 2008 19:26:02 GMT
On Thu, Feb 14, 2008 at 2:21 PM, Andrew2008
<> wrote:
>  Joshua Slive-2 wrote:
>  >
>  > The problem is almost-certainly that your application is sending the
>  > wrong Content-Type header. For instructions on how to look at the
>  > header, see:
>  >
>  >
>  > That leaves open the question of WHY the wrong content-type is being
>  > sent. If you want help about that, you need to give us some details on
>  > exactly what process is generating the content and how it is related
>  > to apache. A simple list of loaded modules doesn't tell us anything at
>  > all.
>  > Joshua.
>  >
>  Sorry, let me give an overview of what i'm doing.  I have a 3rd party
>  application running on Weblogic.  I have Apache running on a different
>  machine and ProxyPass and ProxyPassReverse in my httpd.conf that points to
>  that application running on Weblogic. The reason I'm doing this is because
>  I'm integrating Sun's Access Manager into our application.  Anyway, the
>  application displays fine on weblogic but when it ProxyPassReverse back to
>  Apache then it does not display properly.
>  This is the header section of the html file
>  <META HTTP-EQUIV="Pragma" CONTENT="no-cache">
>  <META HTTP-EQUIV="Content-Control" CONTENT="no-cache">
>  <META HTTP-EQUIV="Cache-Control" CONTENT="no-cache,no-store">
>  <META HTTP-EQUIV="Expires" CONTENT="0">
>  <head>
>  <META http-equiv="Content-Type" content="text/html; charset=UTF-8">
>  <title>Welcome Test</title>
>  <link rel="stylesheet" type="TEXT/CSS" href="/rbs/css/bonaire.css">
>  <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
>  I did not change alot in my httpd.conf file except putting in the ProxyPass
>  and ProxyPassReverse statements.
>  Hope this helps.  Please let me know if you need more details.

The HTTP-EQUIV stuff in the html headers is irrelevant. You need to
look at the HTTP headers using the instructions provided in the link
that I sent in the last message.

Check the headers when connecting directly to your back-end machine,
then check the headers after they are processed by apache.

In the case that apache is really messing up the headers, start by
upgrading to the latest version. Especially if you are using caching,
there have been lots of improvements and bug fixes in recent versions.
I wouldn't consider using mod_cache unless I was using a recent 2.2


The official User-To-User support forum of the Apache HTTP Server Project.
See <URL:> for more info.
To unsubscribe, e-mail:
   "   from the digest:
For additional commands, e-mail:

View raw message