JavaScriptES6FetchAPI时需要注意的一个Cookie问题是怎样的

JavaScript ES6 Fetch API时需要注意的一个Cookie问题是怎样的，相信很多没有经验的人对此束手无策，为此本文总结了问题出现的原因和解决方法，通过这篇文章希望你能解决这个问题。

创新互联公司网站建设公司，提供成都网站建设、做网站，网页设计，建网站，PHP网站建设等专业做网站服务;可快速的进行网站开发网页制作和功能扩展；专业做搜索引擎喜爱的网站，是专业的做网站团队，希望更多企业前来合作!

When I am doing a test of comparison between Stateful and Stateless BSP application ( mentioned in blog  Stateless and Stateful – Different behavior in application side ), I meet with a strange issue.

The conclusion is stateful BSP application will handle request sequentially. Suppose in client I send two request A and B to server. Request A takes 3 seconds to finish and B 2 seconds.

JavaScript ES6 Fetch API时需要注意的一个Cookie问题是怎样的

The request is sent via jQuery API. It means for stateful application, I will observe the following timeline in Chrome network tab:

(1) the start time of both request are almost the same, since I send out two request in client code almost at the same time. (2) even though the second request itself takes 2 seconds to finish, the total processing time for it is 3 seconds waiting for A to finish first + 2 seconds = 5 seconds in the end.

JavaScript ES6 Fetch API时需要注意的一个Cookie问题是怎样的

The above test did verify the conclusion. However when I change the approach to send request into ES6 fetch API,

<%@page language="abap" %><%@extension name="htmlb" prefix="htmlb" %><!DOCTYPE html><html><head><title>Jerry Test Stateful</title></head><body><button onclick="fire()">Fire two request</button><script>function wrapperOnFetch(url){
  fetch(url).then(function(response){
    return response.json();
  }).then(function(json){
      console.log(url + ":" + json.message);
  });}function fire(){
  wrapperOnFetch("first.json");
  wrapperOnFetch("second.json");}</script></body></html>

the testing request for stateful application looks as below this time:

JavaScript ES6 Fetch API时需要注意的一个Cookie问题是怎样的

The two requests are handled simultaneously ( request B only takes 2 seconds to finish, no 3 seconds’ wait time for A to finish this time ), the response of second request returns first before the first, which could be observed in console:

JavaScript ES6 Fetch API时需要注意的一个Cookie问题是怎样的

why the latest ES6 API causes such discrepancy with known conclusion? Just compare the cookie of requests sent via these two kinds of API:

JavaScript ES6 Fetch API时需要注意的一个Cookie问题是怎样的JavaScript ES6 Fetch API时需要注意的一个Cookie问题是怎样的

Through comparison I get to know that the session cookie sap-contextid is not sent together with request triggered by ES6 Fetch API. Then in  Fetch documentation I find out that I need to add option credentials: “include”.

JavaScript ES6 Fetch API时需要注意的一个Cookie问题是怎样的

function wrapperOnFetch(url){
 // enable session cookie sent with request  fetch(url,{ credentials:"include" }).then(function(response){
    return response.json();
  }).then(function(json){
      console.log(url + ":" + json.message);
  });}

After this change the stateful BSP application behaves as expected: the requests are handled in sequence.

看完上述内容，你们掌握JavaScript ES6 Fetch API时需要注意的一个Cookie问题是怎样的的方法了吗？如果还想学到更多技能或想了解更多相关内容，欢迎关注创新互联行业资讯频道，感谢各位的阅读！

网站名称：JavaScriptES6FetchAPI时需要注意的一个Cookie问题是怎样的
本文URL：https://www.cdcxhl.com/article40/jiceeo.html

成都网站建设公司_创新互联，为您提供移动网站建设、商城网站、品牌网站设计、Google、用户体验、软件开发

广告

声明：本网站发布的内容（图片、视频和文字）以用户投稿、用户转载内容为主，如果涉及侵权请尽快告知，我们将会在第一时间删除。文章观点不代表本网站立场，如需处理请联系客服。电话：028-86922220；邮箱：631063699@qq.com。内容未经允许不得转载，或转载时需注明来源： 创新互联

猜你还喜欢下面的内容

营销型网站建设

网站设计公司知识

同城分类信息