互联网技术-alibaba-gateway网关中统一配置跨域请求

扇贝壳

已于 2022-06-28 15:51:59 修改

阅读量428

点赞数

分类专栏： alibaba-gateway alibaba-nacos 远程调用文章标签： java maven spring cloud 阿里云 spring boot

于 2022-06-28 15:49:59 首次发布

本文链接：https://blog.csdn.net/m0_66379583/article/details/125503793

版权

alibaba-nacos 同时被 3 个专栏收录

5 篇文章 0 订阅

订阅专栏

远程调用

5 篇文章 0 订阅

订阅专栏

alibaba-gateway

4 篇文章 0 订阅

订阅专栏

本文介绍了如何在Spring Cloud Gateway中配置全局CORS，包括YML文件设置详细参数和编写配置类的方法。重点讲解了如何处理跨域请求，如允许的域名、HTTP方法和头信息，并展示了两种实现方式。

摘要由CSDN通过智能技术生成

1.添加pom坐标

    <dependencies>
        <!-- 网关 -->
        <dependency>
            <groupId>org.springframework.cloud</groupId>
            <artifactId>spring-cloud-starter-gateway</artifactId>
        </dependency>

        <!-- nacos 服务发现 -->
        <dependency>
            <groupId>com.alibaba.cloud</groupId>
            <artifactId>spring-cloud-starter-alibaba-nacos-discovery</artifactId>
        </dependency>

    </dependencies>

方法一: yml文件

2.yml文件配置添加

spring:
  cloud:
    gateway: 
      globalcors:
        cors-configurations:
          '[/**]':
            allowedOrigins: "*"   # 允许那些网站的跨域请求
            allowedMethods: "*"   # 允许的跨域ajax的请求方式
            allowedHeaders: "*"   # 允许在请求中携带的头信息

2.1yml文件进行详细设置

spring:
  cloud:
    gateway:
      globalcors:
        add-to-simple-url-handler-mapping: true   #解决options请求被拦截
        cors-configurations:
          '[/**]':
            allowedOrigins: "http://localhost:8080"   # 允许那些网站的跨域请求
            allowedMethods:           # 允许的跨域ajax的请求方式
              - GET
              - POST
            allowedHeaders: "*"       # 允许在请求中携带的头信息
            allowCredentials: true	  # 是否允许携带Cookie

方法二: 书写配置类

package com.czxy.config;

import org.springframework.context.annotation.Bean;
import org.springframework.context.annotation.Configuration;
import org.springframework.http.HttpHeaders;
import org.springframework.http.HttpMethod;
import org.springframework.http.HttpStatus;
import org.springframework.http.server.reactive.ServerHttpRequest;
import org.springframework.http.server.reactive.ServerHttpResponse;
import org.springframework.web.cors.reactive.CorsUtils;
import org.springframework.web.server.ServerWebExchange;
import org.springframework.web.server.WebFilter;
import org.springframework.web.server.WebFilterChain;
import reactor.core.publisher.Mono;

/**
 * @author 桐叔
 * @email liangtong@itcast.cn
 */
@Configuration
public class GlobalCorsConfig {

    @Bean
    public WebFilter corsFilter2() {
        return (ServerWebExchange ctx, WebFilterChain chain) -> {
            ServerHttpRequest request = ctx.getRequest();
            if (CorsUtils.isCorsRequest(request)) {
                HttpHeaders requestHeaders = request.getHeaders();
                ServerHttpResponse response = ctx.getResponse();
                HttpMethod requestMethod = requestHeaders.getAccessControlRequestMethod();
                HttpHeaders headers = response.getHeaders();
                headers.add(HttpHeaders.ACCESS_CONTROL_ALLOW_ORIGIN, requestHeaders.getOrigin());
                headers.addAll(HttpHeaders.ACCESS_CONTROL_ALLOW_HEADERS,
                        requestHeaders.getAccessControlRequestHeaders());
                if (requestMethod != null) {
                    headers.add(HttpHeaders.ACCESS_CONTROL_ALLOW_METHODS, requestMethod.name());
                }
                headers.add(HttpHeaders.ACCESS_CONTROL_ALLOW_CREDENTIALS, "true");
                headers.add(HttpHeaders.ACCESS_CONTROL_EXPOSE_HEADERS, "*");
                if (request.getMethod() == HttpMethod.OPTIONS) {
                    response.setStatusCode(HttpStatus.OK);
                    return Mono.empty();
                }
            }
            return chain.filter(ctx);
        };
    }

}