Thanks, Spencer. Do you have the syntax for adding a port number to the img
src line that called CFEngine.nlm?

From: "Spencer Gunn" <spencer@connectotel.demon.co.uk>
Subject: Re: Port blocked by BM37SP3 but not BM37SP2
Date: February 24, 2005 10:56 AM


As a work around you could change the img src link
to specify the 8081 port so that the browser asks
the ContentFilter directly for the image.

Spencer

dmundrick@rockyview.ab.ca wrote:
> We have 34 Border Manager servers on different sites, each configured
> without filtering. We recently installed Connectotel Content Filtering
> and
> it works fabulously! Except for one small problem. On the servers where
> BM37SP2 is installed, the error page (403, for example) loads with a 403
> message and also a logo which is called by an img src html tag that
> references their CFILTER.NLM.
>
> As soon as we install SP3, the logo no longer loads.
>
> Content Filter is a CERN filter that points to port 8081. The Border
> Manager listens to requests on port 8080. If I point my browser to post
> 8080 (the correct configuration), the logo does not load. If I point my
> browser to port 8081 (bypassing my BM Proxy), the logo loads.
>
> I have Connectotel working on this as well, but was hoping that perhaps
> somebody might know a significant difference between SP2 and SP3 that
> might
> cause this. No other changes were made to the Border Manager servers and
> the installation did not make any changes to any NetWare files.