I would think there is a way within Peoplesoft to configure the app to use standard port 80 references to itself instead of port 8080 (even if it's listening on port 8080). If you do want to fix this with LTM, you could use an iRule which rewrites the response headers and content using a stream profile and STREAM::expression iRule:
when HTTP_RESPONSE {
Rewrite redirects to remove the pool member's port
From http://devcentral.f5.com/wiki/default.aspx/iRules/RewriteHTTPRedirectPort.html
Check if server response is a redirect
if { [HTTP::header is_redirect]} {
Log original and updated values
log local0. "Original Location header value: [HTTP::header value Location],\
updated: [string map ":[TCP::remote_port]/ /" [HTTP::header value Location]]"
Do the update, replacing :8080/ with /
HTTP::header replace Location [string map ":[TCP::remote_port]/ /" [HTTP::header value Location]]
}
Remove any instance of the pool member's port from response content
This requires adding a blank stream profile to the virtual server
From http://devcentral.f5.com/wiki/default.aspx/iRules/stream__expression
Check if response type is text
if {[HTTP::header value Content-Type] contains "text"}{
Replace :8080/ with /
STREAM::expression "@:[TCP::remote_port]/@/@"
Enable the stream filter for this response only
STREAM::enable
} else {
Disable the stream filter by default
STREAM::disable
}
}
Aaron