사용자 지정 요청 및 응답 필터
들어오는 요청이나 나가는 응답을 수정하는 특정 로직을 주입하도록 직접 사용자 지정 필터를 개발해 보세요.
사용자 지정 요청 및 응답 필터은(는) CoddyKit의 무료 API Gateway & Reverse Proxy (Nginx + Spring Cloud Gateway) 강의입니다. 이것은 4개 중 2번째 강의입니다. 아래에서 전체 강의를 무료로 읽을 수 있으며, 내장 코드 에디터와 24/7 AI 튜터와 함께 브라우저에서 직접 실습할 수 있습니다. 이 강의는 API Gateway & Reverse Proxy (Nginx + Spring Cloud Gateway) 학습 경로의 일부이며, 진행 상황이 웹과 CoddyKit 앱에 동기화됩니다. API Gateway & Reverse Proxy (Nginx + Spring Cloud Gateway) 강의에는 총 4개의 강의가 포함되어 있습니다.
이 강의의 일부는 아직 번역되지 않았으며 영어로 표시됩니다.
Why Custom Filters?
Spring Cloud Gateway offers many built-in filters, but sometimes you need very specific logic. Custom filters let you inject your own code into the request/response flow.
This allows for highly tailored processing, such as custom authentication checks, unique logging formats, or specific header manipulations.
The GatewayFilter Interface
To create a custom filter, you'll implement the GatewayFilter interface. This interface has one main method: filter().
ServerWebExchange exchange: Provides access to the HTTP request and response.GatewayFilterChain chain: Allows you to pass the request to the next filter or the target service.
You'll also often implement Ordered to define your filter's execution priority.
Basic Request Logger Filter
Let's create a simple filter that logs the incoming request path and method. This filter will run before the request is forwarded to the backend service.
Notice how chain.filter(exchange) is called to continue the processing.
import org.springframework.cloud.gateway.filter.GatewayFilter;
import org.springframework.cloud.gateway.filter.GatewayFilterChain;
import org.springframework.core.Ordered;
import org.springframework.web.server.ServerWebExchange;
import reactor.core.publisher.Mono;
public class MyLoggingFilter implements GatewayFilter, Ordered {
@Override
public Mono<Void> filter(ServerWebExchange exchange, GatewayFilterChain chain) {
System.out.println("Incoming Request:");
System.out.println(" Path: " + exchange.getRequest().getPath());
System.out.println(" Method: " + exchange.getRequest().getMethod());
return chain.filter(exchange); // Pass to next filter/service
}
@Override
public int getOrder() {
return -1; // Execute early
}
public static void main(String[] args) {
MyLoggingFilter filter = new MyLoggingFilter();
System.out.println("This filter logs request details.");
System.out.println("In a Spring Gateway app, this code runs for each matched request.");
System.out.println("The 'filter' method is the core logic, 'getOrder' sets priority.");
}
}Registering Your Custom Filter
Once you've created your filter class, you need to tell Spring Cloud Gateway to use it. You can register it either in your application.yml or programmatically.
For simple filters, registering directly on a route is common. For more complex, reusable filters, a filter factory is often used (covered later).
spring:
cloud:
gateway:
routes:
- id: my_custom_route
uri: http://localhost:8081
predicates:
- Path=/api/**
filters:
- MyLoggingFilter # Name of your @Component filterAccessing Request & Response
The ServerWebExchange object is your gateway to everything about the current HTTP interaction. It contains the ServerHttpRequest and ServerHttpResponse.
exchange.getRequest(): Get details about the incoming request (headers, body, path).exchange.getResponse(): Modify the outgoing response (headers, status code).
Remember, these are reactive types, so operations often return Mono or Flux.
Modifying Request Headers
You might need to add or modify headers before forwarding a request to a backend service. For example, injecting an authentication token or a tracing ID.
Since ServerHttpRequest is immutable, you must build a new request using mutate() and then update the exchange.
import org.springframework.cloud.gateway.filter.GatewayFilter;
import org.springframework.cloud.gateway.filter.GatewayFilterChain;
import org.springframework.core.Ordered;
import org.springframework.web.server.ServerWebExchange;
import reactor.core.publisher.Mono;
public class AddAuthHeaderFilter implements GatewayFilter, Ordered {
@Override
public Mono<Void> filter(ServerWebExchange exchange, GatewayFilterChain chain) {
String authToken = "my-secret-token-123"; // Get from config/service
ServerWebExchange mutatedExchange = exchange.mutate()
.request(builder -> builder.header("X-Auth-Token", authToken))
.build();
System.out.println("Added X-Auth-Token header to request.");
return chain.filter(mutatedExchange); // Use the mutated exchange
}
@Override
public int getOrder() {
return 0; // After logging, before forwarding
}
public static void main(String[] args) {
AddAuthHeaderFilter filter = new AddAuthHeaderFilter();
System.out.println("This filter adds an 'X-Auth-Token' header.");
System.out.println("It uses 'exchange.mutate().request(...).build()' to modify the request.");
}
}Modifying Response Headers
Custom filters can also modify the response *after* the backend service has sent its reply. This is useful for adding security headers, caching directives, or custom metadata.
The trick is to use exchange.getResponse().beforeCommit() to hook into the response lifecycle, or reactive chaining.
import org.springframework.cloud.gateway.filter.GatewayFilter;
import org.springframework.cloud.gateway.filter.GatewayFilterChain;
import org.springframework.core.Ordered;
import org.springframework.web.server.ServerWebExchange;
import reactor.core.publisher.Mono;
public class AddResponseHeaderFilter implements GatewayFilter, Ordered {
@Override
public Mono<Void> filter(ServerWebExchange exchange, GatewayFilterChain chain) {
return chain.filter(exchange).then(Mono.fromRunnable(() -> {
// This code runs AFTER the response from backend is received
exchange.getResponse().getHeaders().add("X-Gateway-Processed", "true");
System.out.println("Added X-Gateway-Processed header to response.");
}));
}
@Override
public int getOrder() {
return 1; // After request processing
}
public static void main(String[] args) {
AddResponseHeaderFilter filter = new AddResponseHeaderFilter();
System.out.println("This filter adds 'X-Gateway-Processed' to the response.");
System.out.println("It uses 'chain.filter(exchange).then(Mono.fromRunnable(...))' for post-processing.");
}
}Controlling Filter Order
When you have multiple custom filters, their execution order matters. The Ordered interface (and its getOrder() method) lets you define this.
- Lower values (e.g.,
-1) mean higher priority (execute earlier). - Higher values (e.g.,
1) mean lower priority (execute later). - Filters with the same order might run in an undefined sequence.
Use Ordered.HIGHEST_PRECEDENCE or LOWEST_PRECEDENCE for extreme cases.
Custom GatewayFilter Factories
For more advanced scenarios, especially when your filter needs configuration (e.g., a specific header name, a threshold value), you can create a GatewayFilterFactory.
This allows you to define a filter with parameters that can be configured directly in your application.yml, making your filters highly reusable and flexible.
You'd extend AbstractGatewayFilterFactory and define a configuration class for its properties.
Filter Logic Check
Consider a custom GatewayFilter that needs to both add a request header and then, after the backend responds, add a response header. Which parts of the filter() method would you modify?
Recap: Custom Filter Power
You've learned how to create custom GatewayFilters in Spring Cloud Gateway. These filters are powerful tools for injecting specific logic into your API Gateway's request and response flow.
- Implement
GatewayFilterandOrdered. - Use
ServerWebExchangefor request/response access. - Mutate requests and use reactive chaining for response modification.
- Control execution order with
getOrder().
Custom filters give you fine-grained control to tailor your gateway's behavior precisely.
자주 묻는 질문
“사용자 지정 요청 및 응답 필터” 강의는 무료인가요?
네 — “사용자 지정 요청 및 응답 필터” 전체 내용을 이 웹사이트에서 무료로 읽을 수 있습니다. 인터랙티브하게 실습하려면(내장 코드 에디터와 24/7 AI 튜터), CoddyKit PRO로 업그레이드하면 API Gateway & Reverse Proxy (Nginx + Spring Cloud Gateway) 강의 전체를 잠금 해제할 수 있습니다. API Gateway & Reverse Proxy (Nginx + Spring Cloud Gateway) 강의에는 총 4개의 강의가 포함되어 있습니다.
“사용자 지정 요청 및 응답 필터”에서 뭘 배우나요?
들어오는 요청이나 나가는 응답을 수정하는 특정 로직을 주입하도록 직접 사용자 지정 필터를 개발해 보세요. 브라우저에서 직접 실행하는 실습 코드로 API Gateway & Reverse Proxy (Nginx + Spring Cloud Gateway)을(를) 배우며, 24/7 AI 튜터가 강의를 진행하면서 질문에 답변해줍니다.
API Gateway & Reverse Proxy (Nginx + Spring Cloud Gateway)을(를) 시작하는 데 경험이 필요한가요?
사전 경험은 필요하지 않습니다. CoddyKit의 API Gateway & Reverse Proxy (Nginx + Spring Cloud Gateway)은(는) 초급자부터 고급 학습자까지를 위해 구성되어 있으므로, 여기서 시작하거나 처음부터 시작할 수 있으며 자신의 속도대로 진행할 수 있습니다. 이것은 4개 중 2번째 강의입니다.
“사용자 지정 요청 및 응답 필터” 강의는 얼마나 걸리나요?
대부분의 CoddyKit 강의는 약 5~10분이 소요됩니다. 각 강의는 간결하고 인터랙티브하여 꾸준한 진행이 가능하며, 웹과 앱에서 중단한 부분부터 바로 시작할 수 있습니다.
이 API Gateway & Reverse Proxy (Nginx + Spring Cloud Gateway) 강의에서 코드를 작성하고 실행할 수 있나요?
네. 모든 API Gateway & Reverse Proxy (Nginx + Spring Cloud Gateway) 강의에는 내장 코드 에디터가 포함되어 있으므로, 브라우저에서 바로 실제 코드를 작성하고 실행한 후 즉시 AI 피드백을 받을 수 있습니다 — 로컬 설정이 필요 없습니다.