2021-04-29

趁今天有空,记录一下自己在做项目的时候遇到的问题吧

项目场景:

我把自己做的停车场项目,改造成Springcloud微服务中遇到的问题


问题描述:

一:前后端跨域问题
前后端跨域是很常见的问题吧,在之前使用SSM框架时,我是通过后端设置请求头来解决的,代码如下,可以成功解决。

 @Override
    public void doFilter(ServletRequest servletRequest, ServletResponse servletResponse, FilterChain filterChain) throws IOException, ServletException {
        HttpServletRequest request = (HttpServletRequest) servletRequest;
        HttpServletResponse httpResponse = (HttpServletResponse) servletResponse;
        httpResponse.addHeader("Access-Control-Allow-Origin", request.getHeader("origin"));
        //httpResponse.setHeader("Access-Control-Allow-Headers", "Origin, X-Requested-With, Content-Type, Accept");
        httpResponse.setHeader("Access-Control-Allow-Headers", "Origin, No-Cache, X-Requested-With, If-Modified-Since, Pragma, Last-Modified, Cache-Control, Expires, Content-Type, X-E4M-With,userId,access_token,refresh_token");
        httpResponse.setHeader("Access-Control-Allow-Methods", "GET, PUT, DELETE, POST");
        httpResponse.setHeader("Access-Control-Allow-Credentials", "true");
        httpResponse.setHeader("Access-Control-Max-Age", "0");
        httpResponse.setContentType("text/html;charset=UTF-8");
        httpResponse.setHeader("XDomainRequestAllowed","1");
        filterChain.doFilter(servletRequest, servletResponse);

    }
本来单体应用设置过滤器就可以了,因为我是改造成微服务架构,使用zuul网关进行过滤,并且把它设置成在路由之前调用,一级执行,然后问题由此产生了。我使用postman测试是没有问题的,但是在前端使用Ajax请求时,就会产生跨域问题,当时百思不得其解。附上我的网关跨域过滤器代码
@Component //跨域过滤器
public class TokenFilter extends ZuulFilter {

   @Override
   public String filterType() {
       return FilterConstants.PRE_TYPE; //在请求被路由之前调用
   }

   @Override
   public int filterOrder() {
       //filter一级执行
       return FilterConstants.PRE_DECORATION_FILTER_ORDER-1;
   }

   @Override
   public boolean shouldFilter() {
       return true;
   }

   @Override
   public Object run() throws ZuulException {
       //获取请求的对香
       RequestContext requestContext = RequestContext.getCurrentContext();
       HttpServletRequest request = requestContext.getRequest();
       HttpServletResponse httpResponse = requestContext.getResponse();

       //配置请求头
       httpResponse.addHeader("Access-Control-Allow-Origin", request.getHeader("origin"));
       //httpResponse.setHeader("Access-Control-Allow-Headers", "Origin, X-Requested-With, Content-Type, Accept");
       httpResponse.setHeader("Access-Control-Allow-Headers", "Origin, No-Cache, X-Requested-With, If-Modified-Since, Pragma, Last-Modified, Cache-Control, Expires, Content-Type, X-E4M-With,userId,access_token,refresh_token");
       httpResponse.setHeader("Access-Control-Allow-Methods", "GET, PUT, DELETE, POST,OPTIONS");
       httpResponse.setHeader("Access-Control-Allow-Credentials", "true");
       httpResponse.setHeader("Access-Control-Max-Age", "0");
       httpResponse.setContentType("text/html;charset=UTF-8;application/json;x-www-form-urlencoded");
       httpResponse.setHeader("XDomainRequestAllowed","1");
       httpResponse.setHeader("X-Content-Type-Options","no-sniff");

       //跨域一共进行两次请求 先发送options 是否可以请求
       //调试可发现一共拦截两次 第一次请求为options,第二次为正常的请求 eg:get请求
       if ("OPTIONS".equalsIgnoreCase(request.getMethod())){
           requestContext.setSendZuulResponse(false);//验证请求不进行路由
           requestContext.setResponseStatusCode(HttpStatus.OK.value());//返回验证成功的状态码
           requestContext.set("isSuccess",true);
           return null;
       }
       //第二次请求
       //无需token验证
       requestContext.setSendZuulResponse(true);//对请求进行路由
       requestContext.setResponseStatusCode(HttpStatus.OK.value());
       requestContext.set("isSuccess",true);
       return null;
   }
}

原因分析:

在chrome进行调试,发现Network中"Access-Control-Allow-Origin"中设置了两次???
发现 “Access-Control-Allow-Origin” :"*"???(找不到截图了抱歉)
小tips:设置为*代表着所有域名都可以访问,一般这么设置是可以的,但是我这么设还是会跨越,而且不安全。
但是我在过滤器中已经设置的是 httpResponse.addHeader(“Access-Control-Allow-Origin”, request.getHeader(“origin”));
即首先动态的获取然后再允许访问


解决方案:

不断的debug然后发现,我是在controller层又加了一个@CrossOrigin注解(被自己蠢哭),因为没有配置注解,所以他又给我改成了**“Access-Control-Allow-Origin” :"*"**。
删掉注解,问题解决。希望对有和我一样问题的小伙伴有帮助吧。

可以使用以下代码将该XML实例转换为application/x-www-form-urlencoded格式的模型: ``` using System.Net.Http; using System.Text; using System.Xml; // 将XML实例转换为application/x-www-form-urlencoded模型 var xmlString = @"<OTA_InventoryCheckRQ EchoToken='487ef6b0-3526-45e3-81e7-0eac31754c10' Password='abc888888' PrimaryLangID='en-us' TimeStamp='2021-04-20 10:30:59' UserName='guowang' Version='1.000'> <POS> <Source> <RequestorID ID='elongID' Type='2'/> </Source> </POS> <HotelReservations> <HotelReservation> <RoomStay> <RoomTypes> <RoomType RoomTypeCode='5412309'/> </RoomTypes> <RatePlans> <RatePlan RatePlanCode='4674478'/> </RatePlans> <GuestCounts> <GuestCount AgeQualifyingCode='10' Count='2'/> <GuestCount AgeQualifyingCode='8' Count='0'/> </GuestCounts> <BasicPropertyInfo HotelCode='2525137'/> </RoomStay> <ResGlobalInfo> <RoomCount>10</RoomCount> <MemberLevel>V1</MemberLevel> <TimeSpan End='2021-04-30' Start='2021-04-29'/> </ResGlobalInfo> </HotelReservation> </HotelReservations> </OTA_InventoryCheckRQ>"; var xmlDoc = new XmlDocument(); xmlDoc.LoadXml(xmlString); var formContent = new FormUrlEncodedContent(new[] { new KeyValuePair<string, string>("Message", xmlDoc.OuterXml) }); var encodedString = formContent.ReadAsStringAsync().Result; Console.WriteLine(encodedString); ``` 输出结果为: ``` Message=%3COTA_InventoryCheckRQ%20EchoToken%3D%22487ef6b0-3526-45e3-81e7-0eac31754c10%22%20Password%3D%22abc888888%22%20PrimaryLangID%3D%22en-us%22%20TimeStamp%3D%222021-04-20%2010%3A30%3A59%22%20UserName%3D%22guowang%22%20Version%3D%221.000%22%3E%3CPOS%3E%3CSource%3E%3CRequestorID%20ID%3D%22elongID%22%20Type%3D%222%22%2F%3E%3C%2FSource%3E%3C%2FPOS%3E%3CHotelReservations%3E%3CHotelReservation%3E%3CRoomStay%3E%3CRoomTypes%3E%3CRoomType%20RoomTypeCode%3D%225412309%22%2F%3E%3C%2FRoomTypes%3E%3CRatePlans%3E%3CRatePlan%20RatePlanCode%3D%224674478%22%2F%3E%3C%2FRatePlans%3E%3CGuestCounts%3E%3CGuestCount%20AgeQualifyingCode%3D%2210%22%20Count%3D%222%22%2F%3E%3CGuestCount%20AgeQualifyingCode%3D%228%22%20Count%3D%220%22%2F%3E%3C%2FGuestCounts%3E%3CBasicPropertyInfo%20HotelCode%3D%222525137%22%2F%3E%3C%2FRoomStay%3E%3CResGlobalInfo%3E%3CRoomCount%3E10%3C%2FRoomCount%3E%3CMemberLevel%3EV1%3C%2FMemberLevel%3E%3CTimeSpan%20End%3D%222021-04-30%22%20Start%3D%222021-04-29%22%2F%3E%3C%2FResGlobalInfo%3E%3C%2FHotelReservation%3E%3C%2FHotelReservations%3E%3C%2FOTA_InventoryCheckRQ%3E ``` 其中,key为"Message",value为对该XML实例进行URL编码后的字符串。
评论 2
添加红包

请填写红包祝福语或标题

红包个数最小为10个

红包金额最低5元

当前余额3.43前往充值 >
需支付:10.00
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明:

1.余额是钱包充值的虚拟货币,按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载,可以购买VIP、付费专栏及课程。

余额充值