When implementing a perimeter service router using wse 3.0 is the following
possible:

A client has to access a remote web service through a perimeter service
router implemented using wse 3.0. The remote web server hosting the
webservice uses basic http authentication (that is Authorization: basic
<base64 encoded user/pass> must be added to the http header).

Coming direcly from the client this seems to be possible by implementing a
custom policy that modifies the WebRequest stored the context of the
SoapElement passed to the ProcessMessage function. On the perimeter serivce
router however the WebRequest is always nothing for all
filters(CreateClientOutputFilter etc.) and even if a SoapHttpRouter is used
the context of the message does not contain a WebRequest instance.

Is there no way of modifying the http header for outgoing requests from a
wse 3.0 perimeter service router? It seems to be impossible to route calls to
webservices that are hosted on remote web servers with base http
authentication enabled.