mirror of
				https://github.com/containous/traefik.git
				synced 2025-11-01 00:23:52 +03:00 
			
		
		
		
	Minor documentation tweaks.
This commit is contained in:
		| @@ -5,9 +5,9 @@ Tweaking the Request | ||||
|  | ||||
|  | ||||
|  | ||||
| Attached to the routers, pieces of middleware are a mean of tweaking the requests before they are sent to your [service](../routing/services/index.md) (or before the answer from the services are sent to the clients). | ||||
| Attached to the routers, pieces of middleware are a means of tweaking the requests before they are sent to your [service](../routing/services/index.md) (or before the answer from the services are sent to the clients). | ||||
|  | ||||
| There are many different available middlewares in Traefik, some can modify the request, the headers, some are in charge of redirections, some add authentication, and so on. | ||||
| There are several available middleware in Traefik, some can modify the request, the headers, some are in charge of redirections, some add authentication, and so on. | ||||
|  | ||||
| Pieces of middleware can be combined in chains to fit every scenario. | ||||
|  | ||||
| @@ -130,7 +130,7 @@ http: | ||||
|  | ||||
| ## Provider Namespace | ||||
|  | ||||
| When you declare a middleware, it lives in its provider namespace. | ||||
| When you declare a middleware, it lives in its provider's namespace. | ||||
| For example, if you declare a middleware using a Docker label, under the hoods, it will reside in the docker provider namespace. | ||||
|  | ||||
| If you use multiple providers and wish to reference a middleware declared in another provider | ||||
|   | ||||
		Reference in New Issue
	
	Block a user