IBM WebSphere XS40, Command Reference Manual

Page: 483 / 1066

Depending on the protocol, the backend service might return a response code that
indicates an error condition. For HTTP messages, the response from the backend
server might include a response body that contains XML that provides more details
about the error.
propagate-uri
Enables or disables the propagation of the local portion of URL from the URL
given by the client to the URL used to contact the backend server.
Syntax
propagate-uri { on | off }
Parameters
on (default) Enables the propagation of the client URI to the backend.
off Disables the propagation of the client URI to the backend.
Guidelines
The propagate-uri command enables or disables the propagation of the client URL
to the backend server.
Enabling URI propagation is meaningful in the following situations only:
v
When the service is configured to use a static backend.
v
When the service is configured to use a dynamic backend and dynamic routing
is set with a route with style sheet (
route-action
) action in the processing
policy. In this case, use the
dp:set-target()
extension element to define that
target backend server.
For the other dynamic routing options that are available with the
route-action
and
route-set
actions, the URI is absolute.
When enabled, the service rewrites the URI of the backend URL to the URI in the
client request. If URI propagation is enabled and the client submits
http://host/service and the backend URL is http://server/listener , the URL is
rewritten to
http://server/service
.
Notes:
1. When enabled, any Matching Rule must match the rewritten URL.
2.
Any action in the Processing Policy can change the URI that is sent to the
backend server. The rewritten URI could override the intended effect of this
setting.
Related Commands
urlrewrite-policy
Examples
v
Disables client URI propagation and subsequently enables such propagation thus
restoring the default state.
# propagate-uri off
.
.
.
# propagate-uri on
#
Chapter 49. Multi-Protocol Gateway configuration mode
457