Return-Path: Delivered-To: apmail-httpd-users-archive@www.apache.org Received: (qmail 47031 invoked from network); 4 Jun 2010 20:43:51 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 4 Jun 2010 20:43:51 -0000 Received: (qmail 62294 invoked by uid 500); 4 Jun 2010 20:43:48 -0000 Delivered-To: apmail-httpd-users-archive@httpd.apache.org Received: (qmail 62275 invoked by uid 500); 4 Jun 2010 20:43:48 -0000 Mailing-List: contact users-help@httpd.apache.org; run by ezmlm Precedence: bulk Reply-To: users@httpd.apache.org list-help: list-unsubscribe: List-Post: List-Id: Delivered-To: mailing list users@httpd.apache.org Received: (qmail 62267 invoked by uid 99); 4 Jun 2010 20:43:48 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 04 Jun 2010 20:43:48 +0000 X-ASF-Spam-Status: No, hits=1.7 required=10.0 tests=AWL,HTML_MESSAGE,RCVD_IN_DNSWL_NONE,SPF_NEUTRAL X-Spam-Check-By: apache.org Received-SPF: neutral (athena.apache.org: local policy) Received: from [74.125.82.173] (HELO mail-wy0-f173.google.com) (74.125.82.173) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 04 Jun 2010 20:43:42 +0000 Received: by wyb36 with SMTP id 36so1123900wyb.18 for ; Fri, 04 Jun 2010 13:43:20 -0700 (PDT) MIME-Version: 1.0 Received: by 10.216.163.204 with SMTP id a54mr91508wel.2.1275684184085; Fri, 04 Jun 2010 13:43:04 -0700 (PDT) Received: by 10.216.87.149 with HTTP; Fri, 4 Jun 2010 13:43:02 -0700 (PDT) Date: Fri, 4 Jun 2010 16:43:02 -0400 Message-ID: From: Duane Winner To: users@httpd.apache.org Content-Type: multipart/alternative; boundary=0016367f9f6ea513e104883a5e38 Subject: [users@httpd] reverse proxy and file download problems for the client --0016367f9f6ea513e104883a5e38 Content-Type: text/plain; charset=ISO-8859-1 We are running apache as a reverse proxy front-end in our DMZ to forward requests to apache servers in our back-end network segment. Previously, until a few months ago, we ran one apache instance for each client in the DMZ without reverse proxy, so the apache was both the front-end and the app server (cgi-bin). One of our clients claims that ever since we moved to reverse proxy structure ago, they are having trouble opening files in Internet Explorer -- it sounds like PDF's only. They say they can "Save to disk", then open, but can't click on URLS and open. They say they don't have issues with Word documents. We asked them to try different browsers and pdf readers, and they report back that it works ok with Firefox and FoxIt Reader w/ Internet Explorer. Because they keep claiming it started when we moved to a reverse proxy structure, we decided to at least test this and set up a test replica of their web app using the old architecture, all in the DMZ They say IE->Acrobat file opens ok on this test bed. So it seems there might be something going on w/ reverse proxy, but I'm clueless as to what. The fact that they can open with Firefox and IE->Foxt Reader still leaves me skeptical that it's our issue, but I can't deny that they proved it works ok when not doing reverse-proxy. The mime types in httpd.conf are configured the same in both instances, and that's the only configuration area I can think of to play around with, but since they're identical, I don't see what I can try. Suggestions, ideas? --0016367f9f6ea513e104883a5e38 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable We are running apache as a reverse proxy front-end in our DMZ to forward re= quests to apache servers in our back-end network segment.

Previously= , until a few months ago, we ran one apache instance for each client in the= DMZ without reverse proxy, so the apache was both the front-end and the ap= p server (cgi-bin).

One of our clients claims that ever since we moved to reverse proxy str= ucture ago, they are having trouble opening files in Internet Explorer -- i= t sounds like PDF's only. They say they can "Save to disk", t= hen open, but can't click on URLS and open.
They say they don't have issues with Word documents.

We asked th= em to try different browsers and pdf readers, and they report back that it = works ok with Firefox and FoxIt Reader w/ Internet Explorer.

Because= they keep claiming it started when we moved to a reverse proxy structure, = we decided to at least test this and set up a test replica of their web app= using the old architecture, all in the DMZ
They say IE->Acrobat file opens ok on this test bed.

So it seems there might be something going on w/ reverse proxy, but I&#= 39;m clueless as to what.

The fact that they can open with Firefox a= nd IE->Foxt Reader still leaves me skeptical that it's our issue, bu= t I can't deny that they proved it works ok when not doing reverse-prox= y.

The mime types in httpd.conf are configured the same in both instances,= and that's the only configuration area I can think of to play around w= ith, but since they're identical, I don't see what I can try.

Suggestions, ideas?
--0016367f9f6ea513e104883a5e38--