Forum Discussion
URL redirection not working after upgrade
I'm not quite sure how that works.
I've taken another tact given the new insights herein.
The new issue I'm having is my string replacement does not appear to be functioning, my redirect appears to remain unvaried
When STREAM_MATCHED {
Insert $myVar to the URI component of the HREF following
the junction /Junction/ for subsequent ingress processing
set myVar [string tolower [getfield [STREAM::match] "." 1]]
STREAM::replace "external.domain.name/Junction/$myVar/"
}when HTTP_REQUEST {
Disable the stream filter for all requests via VS
STREAM::disable
Check URI for part of myVar (nodename01 to nodename19)
if {[HTTP::uri] contains "nodename"}{
set myVarCookie [getfield [HTTP::uri] "/" 3]
Set & Insert Cookie for processing
HTTP::cookie insert name "EV" value $myVar path "/"
Redirect client for processing by the Internal VS
ideally the preceding / needs to be removed after myVar as well
HTTP::redirect [string map {$myVar ""} [HTTP::uri]]
}
}
when HTTP_RESPONSE {
Disable the stream filter by default
STREAM::disable
Enable the stream filter for text responses only
if {[HTTP::header value Content-Type] contains "text"}{
Find the value I want to change, but manage change in STREAM_MATCHED
STREAM::expression {@string@@}
Enable the stream filter for this response only
STREAM::enable
}
}
- SergioPontes_36Oct 06, 2018
Nimbostratus
OK. I found it strange because I'm in version 14 and even without activating application security synchronization, the policies I created on the active device were replicated to Standby. Is there anything more specific that is updated if I enable application security synchronization?
My question would be this. What is actually synchronized in the ASM module only with traditional HA configurations, and what is synchronized after I enable application security synchronization?
- Simon_BlakelyOct 08, 2018
Employee
Did you verify that the actual ASM Policy content was synced, or was it just the policy name attached to an empty policy?
An ASM policy consists of an entry in the
, which just tells mcpd that there is an ASM policy of that name, and an ASM database entry. If mcpd sees ASM policy names inbigip.conf
without the matching ASM database policy data, the policies will be auto-created as empty (and transparent) ASM policies.bigip.conf
The actual policy configuration settings are stored by ASM in a mysql database - this is what is managed by ASM policy synchronization.
I suspect that you managed to sync the policy names but not the Policy settings.
Of course, it could be a new issue. you can find the manual on v14.0 ASM sync here
- SergioPontes_36Oct 08, 2018
Nimbostratus
Many thanks for you support. I think it has now been well explained.
Recent Discussions
Related Content
* 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