we are currently trying to deploy birt 4.2.0 with report viewer in an infrastructure with an upstream propritary load balancer that does https terminiation. the problem is that the html structure is written correctly, but resources (images, css and js) are referencing the terminated url.
A request to url
h t t p s://someserver/portal/reporting/frameset?__id=viewer&__report=SomeReport.rptdesign&__masterpage=true&__locale=de_DE
is tranformed to
h t t p://someserver/portal/reporting/frameset?__id=viewer&__report=SomeReport.rptdesign&__masterpage=true&__locale=de_DE
resources are then requested using the already terminated url which is not reachable from the client:
h t t p://someserver:80/portal/reporting/webcontent/birt/...
the problem seems to be that <BASE> html tag in various JSP files (including RunFragment.jsp) produces a static path based on information from the request:
// base href can be defined in config file for deployment.
String baseHref = request.getScheme( ) + "://" + request.getServerName( ) + ":" + request.getServerPort( );
if( !attributeBean.isDesigner( ) )
String baseURL = ParameterAccessor.getBaseURL( );
if( baseURL != null )
baseHref = baseURL;
baseHref += request.getContextPath( ) + fragment.getJSPRootPath( );
<BASE href="<%= baseHref %>" >
by setting the base_url property in viewer.properties to an empty string, one can achieve the <BASE> to be relative, which, however, is not a cross-browser-solution (IE seems to have problems with it and relative BASE uris seem not to be in scope of HTML 4.01 at all). has anyone had similar problems or am i missing something obvious? many thx.