Forum Discussion
GavinW_29074
Nimbostratus
Feb 17, 2012Another ProxyPass issue :(
Me again...
I've hit another issue with the ProxyPassv10 iRule...
Currently, we've got several VIP's set-up using the ProxyPass irule.
One of these VIPs is set-up as follows:
list /ltm virtual TfGM_CMS.app/service.card.co.uk_https
ltm virtual TfGM_CMS.app/service.card.co.uk_https {
app-service /Common/TfGM_CMS.app/TfGM_CMS
destination 172.16.26.11:https
ip-protocol tcp
mask 255.255.255.255
pool TfGM_CMS.app/TfGM_CMS_pool
profiles {
HTTP_Rewrite { }
TfGM_CMS.app/cmsws_gmpte_card_co_uk_ssl {
context clientside
}
oneconnect { }
stream { }
tcp-wan-optimized { }
wan-optimized-compression { }
}
rules {
ProxyPass
SplunkHTTP
CatchErrors
HeaderStripping
MaintenancePage
HandleErrors
ClientSSLVerification
}
snat automap
vlans-disabled
}
The data-group used by the ProxyPass rule on this VIP contains:
list /ltm data-group internal ProxyPass_cmsws
ltm data-group internal ProxyPass_cmsws {
records {
/CMSBureauWebService/CMSBureauWS {
data /CMSBureauWebService/CardBureauService
}
/CMSBureauWebService/CardBureauService {
data /CMSBureauWebService/CardBureauService
}
/CMSWebPortalService/CardRenewalWebPortal_2_0 {
data /CMSWebPortalService/CardRenewalWebPortal_2_0
}
/CMSWebPortalService/VoucherRedemptionService {
data /CMSWebPortalService/VoucherRedemptionService
}
/CMSWebPortalService/WebPortalService {
data /CMSWebPortalService/WebPortalService
}
}
type string
}
RewriteResponsePayload is set to a value of 2, and the VIP has a Stream profile attached.
However I'm still seeing the following errors logged on making requests:
Feb 17 15:50:04 tmm3 info tmm3[9382]: Rule /Common/ProxyPass : VS=/Common/TfGM_CMS.app/service.card.co.uk_https, Host=service.card.co.uk, URI=/CMSBureauWebService/CMSBureauWS: Error setting stream expression (). If you enable static::RewriteResponsePayload, then you should add a stream profile to the VIP. Else, set static::RewriteResponsePayload to 0 in this iRule.
If I enable verbose logging, I get:
Feb 17 15:50:04 tmm3 info tmm3[9382]: Rule /Common/ProxyPass : Processing HTTP_RESPONSE at Priority 900.
Feb 17 15:50:04 tmm3 info tmm3[9382]: Rule /Common/ProxyPass : VS=/Common/TfGM_CMS.app/service.card.co.uk_https, Host=service.card.co.uk, URI=/CMSBureauWebService/CMSBureauWS: $stream_expression_cmd: STREAM::expression "@https?://service.card.co.uk/CMSBureauWebService/CardBureauService@https://service.card.co.uk/CMSBureauWebService/CMSBureauWS@ @https?%3A%2F%2Fservice.card.co.uk%2FCMSBureauWebService%2FCardBureauService@https%3a%2f%2fservice.card.co.uk%2fCMSBureauWebService%2fCMSBureauWS@ @/CMSBureauWebService/CardBureauService@/CMSBureauWebService/CMSBureauWS@ @%2FCMSBureauWebService%2FCardBureauService@%2fCMSBureauWebService%2fCMSBureauWS@", $stream_enable_cmd: STREAM::enable
Feb 17 15:50:04 tmm3 info tmm3[9382]: Rule /Common/ProxyPass : VS=/Common/TfGM_CMS.app/service.card.co.uk_https, Host=service.card.co.uk, URI=/CMSBureauWebService/CMSBureauWS: Error setting stream expression (). If you enable static::RewriteResponsePayload, then you should add a stream profile to the VIP. Else, set static::RewriteResponsePayload to 0 in this iRule.
I cant see any issues with the STREAM::expression value of the STREAM::cmd...
Any ideas what could be causing the above error?
Regards
Gavin
2 Replies
- hoolio
Cirrostratus
Hi Gavin,
Are you customizing the STREAM::expression somewhere? I was able to set the stream expression to yours on a test virtual server and it worked:
when HTTP_RESPONSE {
STREAM::expression "@https?://service.card.co.uk/CMSBureauWebService/CardBureauService@https://service.card.co.uk/CMSBureauWebService/CMSBureauWS@ @https?%3A%2F%2Fservice.card.co.uk%2FCMSBureauWebService%2FCardBureauService@https%3a%2f%2fservice.card.co.uk%2fCMSBureauWebService%2fCMSBureauWS@ @/CMSBureauWebService/CardBureauService@/CMSBureauWebService/CMSBureauWS@ @%2FCMSBureauWebService%2FCardBureauService@%2fCMSBureauWebService%2fCMSBureauWS@"
STREAM::enable
}
Aaron - GavinW_29074
Nimbostratus
Aaron
Nope, the ProxyPass rule is the only rule that uses STREAM expressions...
However I've noticed today that the log errors have stopped, with no other changes being made... So not sure what happened there, but it looks like it's resolved itself :s
Gav
Recent Discussions
Related Content
DevCentral Quicklinks
* Getting Started on DevCentral
* Community Guidelines
* Community Terms of Use / EULA
* Community Ranking Explained
* Community Resources
* Contact the DevCentral Team
* Update MFA on account.f5.com
Discover DevCentral Connects
