Description Paul Kofon 2010-07-16 11:00:16 EDT

Build Identifier: 2.3.2

In our setup, we have a firewall (Microsoft ISA) running on a machine
with a public IP address and we have enabled port forwarding as BIRT
runs on a local server (Tomcat 6.0.20).
We have no issues running/viewing reports on the LAN. For instance, we
can access BIRT reports like this:
http://reportserver:9090/birt/frameset?__report=report/app/a cct_stmt.rptdesign&id=1001&from_date=2010-01-01& to_date=2010-07-14


(Note that this is done via a GUI application that runs on the same
machine as BIRT, so users don't have to enter the URL manually. They can
log into this application and navigate it from outside successfully via
the firewall with the public IP Address).

However, reports cannot be run from the Internet using, for instance, the
following URL:

http://public_ip/birt/frameset?__report=report/app/acct_stmt .rptdesign&id=1001&from_date=2010-01-01&to_date= 2010-07-14
(where public_ip is the public IP Address assigned to the firewall machine)

When a user attempts to run a report, nothing shows up and the browser
just keeps loading and waiting for a response... In Firebug I can see that the first request to
/birt/frameset is OK. However, the first of many requests that BIRT makes goes to
http://[192.168.0.4:9090]/birt/webcontent/birt/styles/style.cs s, which is
our local server! And of course there are other additional requests (for
stylesheets and javascript files) which also go to the local server.

Reproducible: Always

Steps to Reproduce:
1. Deploy BIRT as a war on Tomcat
2. Setup firewall (Microsoft ISA)
3. Access BIRT reports via firewall with the /frameset mapping