If more fine-grained ignoring is needed, you can specify specific patterns to ignore. These patterns are being evaluated at the end of the route location process, which means prefixes should be included in the pattern to warrant a match. Ignored patterns span all services and supersede any other route specification.

zuul:
  ignoredPatterns: */admin/**
  routes:
    users: /myusers/**

This means that all calls such as "/myusers/101" will be forwarded to "/101" on the "users" service. But calls including "/admin/" will not resolve.
This commit is contained in:
andreasevers
2015-07-27 16:48:26 +02:00
committed by Spencer Gibb
parent 558c78353c
commit 42f6e4d1f0
4 changed files with 203 additions and 21 deletions

View File

@@ -900,6 +900,23 @@ An application with the `@EnableZuulProxy` could act as a standalone
server if you set a default route ("/"), for example `zuul.route.home:
/` would route all traffic (i.e. "/**") to the "home" service.
If more fine-grained ignoring is needed, you can specify specific patterns to ignore.
These patterns are being evaluated at the end of the route location process, which
means prefixes should be included in the pattern to warrant a match. Ignored patterns
span all services and supersede any other route specification.
.application.yml
[source,yaml]
----
zuul:
ignoredPatterns: */admin/**
routes:
users: /myusers/**
----
This means that all calls such as "/myusers/101" will be forwarded to "/101" on the "users" service.
But calls including "/admin/" will not resolve.
=== Uploading Files through Zuul
If you `@EnableZuulProxy` you can use the proxy paths to