| /external/rust/crates/axum/src/docs/ |
| D | middleware.md | 4 - [Applying middleware](#applying-middleware)
5 - [Commonly used middleware](#commonly-used-middleware)
7 - [Writing middleware](#writing-middleware)
8 - [Routing to services/middleware and backpressure](#routing-to-servicesmiddleware-and-backpressure)
9 - [Accessing state in middleware](#accessing-state-in-middleware)
10 - [Passing state from middleware to handlers](#passing-state-from-middleware-to-handlers)
11 - [Rewriting request URI in middleware](#rewriting-request-uri-in-middleware)
15 axum is unique in that it doesn't have its own bespoke middleware system and
17 [`tower-http`] middleware all work with axum.
19 While its not necessary to fully understand tower to write or use middleware
[all …]
|
| D | error_handling.md | 7 - [Applying fallible middleware](#applying-fallible-middleware)
60 applying middleware, which might produce errors you have to tell axum how to
103 # Applying fallible middleware
105 Similarly axum requires you to handle errors from middleware. That is done with
|
| /external/rust/crates/axum/src/docs/routing/ |
| D | layer.md | 6 Note that the middleware is only applied to existing routes. So you have to
8 routes added after `layer` is called will not have the middleware added.
10 If you want to add middleware to a single handler you can either use
28 If you need to write your own middleware see ["Writing
29 middleware"](crate::middleware#writing-middleware) for the different options.
31 If you only want middleware on some routes you can use [`Router::merge`]:
52 # Multiple middleware
55 middleware. See [`middleware`](crate::middleware) for more details.
59 Middleware added with this method will run _after_ routing and thus cannot be
61 middleware"](crate::middleware#rewriting-request-uri-in-middleware) for more
[all …]
|
| D | route_layer.md | 4 Note that the middleware is only applied to existing routes. So you have to
6 routes added after `layer` is called will not have the middleware added.
8 This works similarly to [`Router::layer`] except the middleware will only run if
9 the request matches a route. This is useful for middleware that return early
|
| /external/rust/crates/axum/src/ |
| D | service_ext.rs | 11 /// This is commonly used when applying middleware around an entire [`Router`]. See ["Rewriting
12 /// request URI in middleware"] for more details.
15 … /// ["Rewriting request URI in middleware"]: crate::middleware#rewriting-request-uri-in-middleware
24 /// This is commonly used when applying middleware around an entire [`Router`]. See ["Rewriting
25 /// request URI in middleware"] for more details.
28 … /// ["Rewriting request URI in middleware"]: crate::middleware#rewriting-request-uri-in-middleware
|
| D | lib.rs | 14 //! - [Middleware](#middleware)
28 //! middleware, services, and utilities.
31 //! `axum` doesn't have its own middleware system but instead uses
33 //! authorization, and more, for free. It also enables you to share middleware with
164 //! # Middleware
166 //! There are several different ways to write middleware for axum. See
167 //! [`middleware`](crate::middleware) for more details.
251 //! middleware or because you're extracting the wrong type.
459 pub mod middleware; module
|
| /external/rust/crates/tower/ |
| D | README.md | 43 middleware with [`Service`]s. If a [`Service`] can be thought of as an
46 different type. The [`ServiceBuilder`] type is used to add middleware to a
63 middleware, and [utilities] for working with [`Service`]s and [`Layer`]s.
70 middleware. This means that the `tower` crate on its own does *not* provide
73 application code, libraries providing middleware implementations, and
81 the middleware [provided by this crate][all_layers] and by other libraries
84 * **Implementing middleware** to add custom behavior to network clients and
85 servers in a reusable manner. This might be general-purpose middleware
86 (and if it is, please consider releasing your middleware as a library for
93 allowing users to add arbitrary Tower middleware to those clients.
[all …]
|
| D | CHANGELOG.md | 65 `BoxService` and `BoxCloneService` middleware ([#616])
220 that produces middleware of that type, as a convenience to avoid having to
256 middleware into the `tower` crate. In addition, Tower 0.4 reworks several
257 middleware APIs, as well as introducing new ones.
267 - **steer**: Added `steer` middleware for routing requests to one of a set of
269 - **util**: Added `MapRequest` middleware and `ServiceExt::map_request`, for
272 - **util**: Added `MapResponse` middleware and `ServiceExt::map_response`, for
275 - **util**: Added `MapErr` middleware and `ServiceExt::map_err`, for
278 - **util**: Added `MapResult` middleware and `ServiceExt::map_result`, for
281 - **util**: Added `Then` middleware and `ServiceExt::then`, for chaining another
[all …]
|
| /external/rust/crates/tower/src/ |
| D | lib.rs | 32 //! middleware with [`Service`]s. If a [`Service`] can be thought of as an
35 //! different type. The [`ServiceBuilder`] type is used to add middleware to a
52 //! middleware, and [utilities] for working with [`Service`]s and [`Layer`]s.
59 //! middleware. This means that the `tower` crate on its own does *not* provide
62 //! application code, libraries providing middleware implementations, and
70 //! the middleware [provided by this crate](#modules) and by other libraries
73 //! * **Implementing middleware** to add custom behavior to network clients and
74 //! servers in a reusable manner. This might be general-purpose middleware
75 //! (and if it is, please consider releasing your middleware as a library for
82 //! allowing users to add arbitrary Tower middleware to those clients.
[all …]
|
| /external/bazelbuild-rules_python/examples/build_file_generation/ |
| D | gazelle_python.yaml | 83 werkzeug.middleware: Werkzeug
84 werkzeug.middleware.dispatcher: Werkzeug
85 werkzeug.middleware.http_proxy: Werkzeug
86 werkzeug.middleware.lint: Werkzeug
87 werkzeug.middleware.profiler: Werkzeug
88 werkzeug.middleware.proxy_fix: Werkzeug
89 werkzeug.middleware.shared_data: Werkzeug
|
| /external/libwebsockets/contrib/ |
| D | cross-linkit.cmake | 72 …middleware/third_party/lwip/src/include/lwip -I${CROSS_BASE}/middleware/third_party/lwip/src/inclu…
|
| /external/autotest/frontend/ |
| D | settings.py | 103 'django.middleware.common.CommonMiddleware',
104 'django.contrib.sessions.middleware.SessionMiddleware',
106 'django.contrib.auth.middleware.AuthenticationMiddleware',
107 'django.middleware.doc.XViewMiddleware',
108 'django.contrib.messages.middleware.MessageMiddleware',
126 # TODO(scottz): Temporary addition until time can be spent untangling middleware
|
| /external/rust/crates/axum/src/docs/method_routing/ |
| D | route_layer.md | 4 Note that the middleware is only applied to existing routes. So you have to
6 routes added after `layer` is called will not have the middleware added.
8 This works similarly to [`MethodRouter::layer`] except the middleware will only run if
9 the request matches a route. This is useful for middleware that return early
|
| D | layer.md | 6 Note that the middleware is only applied to existing routes. So you have to
8 routes added after `layer` is called will not have the middleware added.
|
| /external/rust/crates/axum/src/middleware/ |
| D | from_fn.rs | 18 /// Create a middleware from an async function.
37 /// middleware::{self, Next},
55 /// .layer(middleware::from_fn(my_middleware));
68 /// middleware::{self, Next},
97 /// .route_layer(middleware::from_fn(auth));
107 /// Create a middleware from an async function with the given state.
119 /// middleware::{self, Next},
147 /// .route_layer(middleware::from_fn_with_state(state.clone(), my_middleware))
161 /// [`tower::Layer`] is used to apply middleware to [`Router`](crate::Router)'s.
215 /// A middleware created from an async function.
[all …]
|
| D | map_request.rs | 17 /// Create a middleware from an async function that transforms a request.
28 /// middleware::map_request,
51 /// middleware.
63 /// middleware::map_request,
94 /// middleware::map_request,
119 /// Create a middleware from an async function that transforms a request, with the given state.
131 /// middleware::map_request_with_state,
219 /// A middleware created from an async function that transforms a request.
|
| D | map_response.rs | 17 /// Create a middleware from an async function that transforms a response.
28 /// middleware::map_response,
52 /// middleware::map_response,
82 /// middleware::map_response,
103 /// Create a middleware from an async function that transforms a response, with the given state.
115 /// middleware::map_response_with_state,
203 /// A middleware created from an async function that transforms a response.
|
| D | mod.rs | 1 //! Utilities for writing middleware
3 #![doc = include_str!("../docs/middleware.md")]
|
| /external/rust/crates/tower/src/builder/ |
| D | mod.rs | 175 /// middleware.
194 /// [`ConcurrencyLimit`] middleware.
208 /// Usually, when a service or middleware does not have capacity to process a
216 /// middleware.
230 /// middleware.
249 /// middleware.
265 /// middleware.
282 /// middleware.
300 /// middleware.
316 /// middleware.
[all …]
|
| /external/rust/crates/tower-layer/src/ |
| D | lib.rs | 15 //! A middleware implements the [`Layer`] and [`Service`] trait.
92 /// log middleware could be used in either a client or a server.
98 /// Wrap the given service with the middleware, returning a new service
99 /// that has been decorated with the middleware.
|
| /external/pigweed/pw_package/ |
| D | docs.rst | 43 .. _module-pw_package-middleware-only-packages:
45 Middleware-Only Packages
133 * ``allow_middleware_only_packages``: Allow middleware-only packages to be
134 installed. See :ref:`module-pw_package-middleware-only-packages` for more.
|
| /external/rust/crates/axum/ |
| D | CHANGELOG.md | 121 - **fixed:** Fix `Allow` missing from routers with middleware ([#1773])
160 - **added:** Implement `Clone` and `Service` for `axum::middleware::Next` ([#1712])
533 - **breaking:** `MatchedPath` can now no longer be extracted in middleware for
535 from a middleware applied to a nested router. `MatchedPath` can still be
536 extracted from handlers and middleware that aren't on nested routers ([#1462])
540 ## Middleware section in 0.6.0 (25. November, 2022)
542 - **added:** Support running extractors on `middleware::from_fn` functions ([#1088])
543 - **added**: Add `middleware::from_fn_with_state` to enable running extractors that require
545 - **added:** Add `middleware::from_extractor_with_state` ([#1396])
550 - **added:** Support any middleware response that implements `IntoResponse` ([#1152])
[all …]
|
| /external/rust/crates/tower-service/ |
| D | README.md | 42 By using standardizing the interface, middleware can be created. Middleware
44 middleware may take actions such as modify the request.
|
| /external/rust/crates/tonic/src/service/ |
| D | interceptor.rs | 1 //! gRPC interceptors which are a kind of middleware.
23 /// gRPC interceptors are similar to middleware but have less flexibility. An interceptor allows
35 /// If you need more powerful middleware, [tower] is the recommended approach. You can find
39 /// a [tower] middleware is more appropriate since it can also act on the response. For example
41 /// middleware supports gRPC out of the box.
90 /// A service wrapped in an interceptor middleware.
|
| /external/python/oauth2client/oauth2client/contrib/django_util/ |
| D | __init__.py | 49 "django.contrib.sessions.middleware"
53 This helper also requires the Django Session Middleware, so
54 ``django.contrib.sessions.middleware`` should be in INSTALLED_APPS as well.
341 if ('django.contrib.sessions.middleware.SessionMiddleware'
344 'The Google OAuth2 Helper requires session middleware to '
346 ' to include \'django.contrib.sessions.middleware.'
|