As GamP points out, the WebFOCUS references are all relative. If that port is being tacked on, its probably because of your application.
If you actually run an HTTP Trace with a tool like
Fiddler2 .
You will see that when you submit a request to the WFServlet for a PDF or XLS it actually creates a simple page like the following:
<HTML>
<Head>
<Title>WebFOCUS Report</Title>
<Script Language="JavaScript">
<!--
function getrep()
{
if(parseInt(window.navigator.appVersion,10)<4)
location.assign("/ibi_apps/WFServlet?PG_REQTYPE=REDIRECT&PG_MRsaved=false&PG_Func=GETBINARY&PG_File=dduxkwqx.pdf");
else
location.replace("/ibi_apps/WFServlet?PG_REQTYPE=REDIRECT&PG_MRsaved=false&PG_Func=GETBINARY&PG_File=dduxkwqx.pdf");
} //-->
</Script></Head>
<body onload="getrep()"></BODY>
</HTML><!--
0 NUMBER OF RECORDS IN TABLE= 18 LINES= 18
0 HOLDING PDF FILE ON PC DISK ...
WebFOCUS Version 7.6.8 compiled and linked on Tue Dec 30 00:34:32 EST 2008 (Gen branch768:141)
-->
That page then redirects to the actual output.
As you can see from this output, the references are completely relative.
I suppose it is always possible if you're using an older release of WebFOCUS that this is not relative in an older release, but I'm pretty sure this goes back some time.
If you add your WebFOCUS release to your signature it would be much easier to assist you with things like this with answers that are release specific.
Thanks,
Doug Logan
WF 71.x, 76.x, 7701, 8.0 Beta OS: Linux, Win2k3, Win2k, Win2k8, WinXP