You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
zuul:
decodeUrl: false
forceOriginalQueryStringEncoding: true
sensitiveHeaders: Cookie,Set-Cookie,Origin
ignoredHeaders: Access-Control-Allow-Origin
ignoreSecurityHeaders: false
# Note that the order below is important for the endpoint to match the correct route.
# Ex. Partner is before Internal so that /third-party is not picked up by /**.
routes:
partner:
path: /gateway/*hird-party/**
internal:
path: /gateway/**
health:
path: /health
strip-prefix: false
appapisregistry:
path: /appapis/featureregistry/**
appapisgetaccountbyid:
path: /appapis/getaccountbyid/**
appapistransactions:
path: /appapis/accounts/**
appapisupcomingtransactions:
path: /appapis/upcoming-transactions/**
appapisaddress:
path: /appapis/customer-addresses/**
appapissummary:
path: /appapis/accountsummary
strip-prefix: false
appapiscookie:
path: /appapis/customer/cookie
strip-prefix: false
appui:
path: /appui/**
strip-prefix: false
appweb:
path: /appweb/**
strip-prefix: false
appindex:
path: /index.html
strip-prefix: false
# Note: This must be the last route configured as it is a catch all.
catchall:
path: /*/*
strip-prefix: false
The text was updated successfully, but these errors were encountered:
Describe the bug
Prior to Hoxton SR5, routes configured in application.yml were evaluated in the order defined in the configuration file.
With SR5, the order doesn't seem to be honored causing legacy routes to get picked up before specific routes.
Sample
Below is a sample output of routing matching for the same route in SR4 and SR5. Route in both cases is /appui/smartBanner.js
SR4
SR5
application.yml
The text was updated successfully, but these errors were encountered: