React跨域調試技巧

場景:使用create-react-app創(chuàng)建項目丹皱,由于前后分離開發(fā)酝静,本地起一個服務http://localhost:3000骄蝇。所以當使用自帶fetch去請求API的時候就存在同源策略跨域問題,今天分享一個跨域調試小技巧谷醉,無需服務端配合致稀。

方法一:

安裝谷歌瀏覽器跨域插件:Allow-Control-Allow-Origin
注意:fetch請求中配置不可填寫credentials: "include"

方法二:

通過proxy解決跨域問題,可以直接在package.json下配置俱尼,具體如下:

"proxy": "http://api.xxxx.com"

滿足可以調用不同域下的API的需求抖单,代碼如下:

//package.json中加入
  "proxy": {
    "/api/RoomApi": {
      "target": "http://api.xxxx.com",
      "changeOrigin":true
    },
    "/api/v1":{
      "target":"http://api.xxxx.com",
      "changeOrigin":true
    }
}

注意:第二種方法fetch在請求的時候要使用相對路徑url,即:url='/master/login'遇八。不可使用全路徑:即:'http://api.xxxx.com/master/login'

我們在實際開發(fā)中矛绘,打包后上傳到同域名路徑就ok了,不需要設置webpack代理的刃永,這時候我們在打包的時候就需要在package.json配置中關閉剛才設置的proxy货矮,挺麻煩的,難免打包的時候忘記屏蔽掉斯够。解決方法:

    
1.你也可以使用 create-react-app 提供的  yarn run eject 命令將所有內建的配置暴露出來
2.修改webpackDevServer.config.js文件添加
```注意:yarn run eject可能導致項目跑不起來囚玫,這時候執(zhí)行yarn 或者 npm install即可 ```

(process.env.NODE_ENV === 'development') && (proxy = {
    "/": {
      "target": "http://api.xxxx.com",
      "changeOrigin": true
    }
  });

webpackDevServer.config.js完整代碼:

'use strict';

const errorOverlayMiddleware = require('react-dev-utils/errorOverlayMiddleware');
const noopServiceWorkerMiddleware = require('react-dev-utils/noopServiceWorkerMiddleware');
const ignoredFiles = require('react-dev-utils/ignoredFiles');
const config = require('./webpack.config.dev');
const paths = require('./paths');

const protocol = process.env.HTTPS === 'true' ? 'https' : 'http';
const host = process.env.HOST || '0.0.0.0';
module.exports = function(proxy, allowedHost) {

  (process.env.NODE_ENV === 'development') && (proxy = {
    "/": {
      "target": "https://echo-dev.skyplan.online",
      "changeOrigin": true
    }
  });
  
  return {
    // WebpackDevServer 2.4.3 introduced a security fix that prevents remote
    // websites from potentially accessing local content through DNS rebinding:
    // https://github.com/webpack/webpack-dev-server/issues/887
    // https://medium.com/webpack/webpack-dev-server-middleware-security-issues-1489d950874a
    // However, it made several existing use cases such as development in cloud
    // environment or subdomains in development significantly more complicated:
    // https://github.com/facebookincubator/create-react-app/issues/2271
    // https://github.com/facebookincubator/create-react-app/issues/2233
    // While we're investigating better solutions, for now we will take a
    // compromise. Since our WDS configuration only serves files in the `public`
    // folder we won't consider accessing them a vulnerability. However, if you
    // use the `proxy` feature, it gets more dangerous because it can expose
    // remote code execution vulnerabilities in backends like Django and Rails.
    // So we will disable the host check normally, but enable it if you have
    // specified the `proxy` setting. Finally, we let you override it if you
    // really know what you're doing with a special environment variable.
    disableHostCheck:
      !proxy || process.env.DANGEROUSLY_DISABLE_HOST_CHECK === 'true',
    // Enable gzip compression of generated files.
    compress: true,
    // Silence WebpackDevServer's own logs since they're generally not useful.
    // It will still show compile warnings and errors with this setting.
    clientLogLevel: 'none',
    // By default WebpackDevServer serves physical files from current directory
    // in addition to all the virtual build products that it serves from memory.
    // This is confusing because those files won’t automatically be available in
    // production build folder unless we copy them. However, copying the whole
    // project directory is dangerous because we may expose sensitive files.
    // Instead, we establish a convention that only files in `public` directory
    // get served. Our build script will copy `public` into the `build` folder.
    // In `index.html`, you can get URL of `public` folder with %PUBLIC_URL%:
    // <link rel="shortcut icon" href="%PUBLIC_URL%/favicon.ico">
    // In JavaScript code, you can access it with `process.env.PUBLIC_URL`.
    // Note that we only recommend to use `public` folder as an escape hatch
    // for files like `favicon.ico`, `manifest.json`, and libraries that are
    // for some reason broken when imported through Webpack. If you just want to
    // use an image, put it in `src` and `import` it from JavaScript instead.
    contentBase: paths.appPublic,
    // By default files from `contentBase` will not trigger a page reload.
    watchContentBase: true,
    // Enable hot reloading server. It will provide /sockjs-node/ endpoint
    // for the WebpackDevServer client so it can learn when the files were
    // updated. The WebpackDevServer client is included as an entry point
    // in the Webpack development configuration. Note that only changes
    // to CSS are currently hot reloaded. JS changes will refresh the browser.
    hot: true,
    // It is important to tell WebpackDevServer to use the same "root" path
    // as we specified in the config. In development, we always serve from /.
    publicPath: config.output.publicPath,
    // WebpackDevServer is noisy by default so we emit custom message instead
    // by listening to the compiler events with `compiler.plugin` calls above.
    quiet: true,
    // Reportedly, this avoids CPU overload on some systems.
    // https://github.com/facebookincubator/create-react-app/issues/293
    // src/node_modules is not ignored to support absolute imports
    // https://github.com/facebookincubator/create-react-app/issues/1065
    watchOptions: {
      ignored: ignoredFiles(paths.appSrc),
    },
    // Enable HTTPS if the HTTPS environment variable is set to 'true'
    https: protocol === 'https',
    host: host,
    overlay: false,
    historyApiFallback: {
      // Paths with dots should still use the history fallback.
      // See https://github.com/facebookincubator/create-react-app/issues/387.
      disableDotRule: true,
    },
    public: allowedHost,
    proxy,
    before(app) {
      // This lets us open files from the runtime error overlay.
      app.use(errorOverlayMiddleware());
      // This service worker file is effectively a 'no-op' that will reset any
      // previous service worker registered for the same host:port combination.
      // We do this in development to avoid hitting the production cache if
      // it used the same host and port.
      // https://github.com/facebookincubator/create-react-app/issues/2272#issuecomment-302832432
      app.use(noopServiceWorkerMiddleware());
    },
  };
};

最后編輯于
?著作權歸作者所有,轉載或內容合作請聯(lián)系作者
  • 序言:七十年代末,一起剝皮案震驚了整個濱河市读规,隨后出現(xiàn)的幾起案子抓督,更是在濱河造成了極大的恐慌,老刑警劉巖束亏,帶你破解...
    沈念sama閱讀 211,194評論 6 490
  • 序言:濱河連續(xù)發(fā)生了三起死亡事件铃在,死亡現(xiàn)場離奇詭異,居然都是意外死亡碍遍,警方通過查閱死者的電腦和手機定铜,發(fā)現(xiàn)死者居然都...
    沈念sama閱讀 90,058評論 2 385
  • 文/潘曉璐 我一進店門,熙熙樓的掌柜王于貴愁眉苦臉地迎上來雀久,“玉大人宿稀,你說我怎么就攤上這事±蛋疲” “怎么了祝沸?”我有些...
    開封第一講書人閱讀 156,780評論 0 346
  • 文/不壞的土叔 我叫張陵,是天一觀的道長越庇。 經常有香客問我罩锐,道長,這世上最難降的妖魔是什么卤唉? 我笑而不...
    開封第一講書人閱讀 56,388評論 1 283
  • 正文 為了忘掉前任涩惑,我火速辦了婚禮,結果婚禮上桑驱,老公的妹妹穿的比我還像新娘竭恬。我一直安慰自己跛蛋,他們只是感情好,可當我...
    茶點故事閱讀 65,430評論 5 384
  • 文/花漫 我一把揭開白布痊硕。 她就那樣靜靜地躺著赊级,像睡著了一般。 火紅的嫁衣襯著肌膚如雪岔绸。 梳的紋絲不亂的頭發(fā)上理逊,一...
    開封第一講書人閱讀 49,764評論 1 290
  • 那天,我揣著相機與錄音盒揉,去河邊找鬼晋被。 笑死,一個胖子當著我的面吹牛刚盈,可吹牛的內容都是我干的羡洛。 我是一名探鬼主播,決...
    沈念sama閱讀 38,907評論 3 406
  • 文/蒼蘭香墨 我猛地睜開眼扁掸,長吁一口氣:“原來是場噩夢啊……” “哼翘县!你這毒婦竟也來了最域?” 一聲冷哼從身側響起谴分,我...
    開封第一講書人閱讀 37,679評論 0 266
  • 序言:老撾萬榮一對情侶失蹤,失蹤者是張志新(化名)和其女友劉穎镀脂,沒想到半個月后牺蹄,有當?shù)厝嗽跇淞掷锇l(fā)現(xiàn)了一具尸體,經...
    沈念sama閱讀 44,122評論 1 303
  • 正文 獨居荒郊野嶺守林人離奇死亡薄翅,尸身上長有42處帶血的膿包…… 初始之章·張勛 以下內容為張勛視角 年9月15日...
    茶點故事閱讀 36,459評論 2 325
  • 正文 我和宋清朗相戀三年沙兰,在試婚紗的時候發(fā)現(xiàn)自己被綠了。 大學時的朋友給我發(fā)了我未婚夫和他白月光在一起吃飯的照片翘魄。...
    茶點故事閱讀 38,605評論 1 340
  • 序言:一個原本活蹦亂跳的男人離奇死亡鼎天,死狀恐怖,靈堂內的尸體忽然破棺而出暑竟,到底是詐尸還是另有隱情斋射,我是刑警寧澤,帶...
    沈念sama閱讀 34,270評論 4 329
  • 正文 年R本政府宣布但荤,位于F島的核電站罗岖,受9級特大地震影響,放射性物質發(fā)生泄漏腹躁。R本人自食惡果不足惜桑包,卻給世界環(huán)境...
    茶點故事閱讀 39,867評論 3 312
  • 文/蒙蒙 一、第九天 我趴在偏房一處隱蔽的房頂上張望纺非。 院中可真熱鬧哑了,春花似錦赘方、人聲如沸。這莊子的主人今日做“春日...
    開封第一講書人閱讀 30,734評論 0 21
  • 文/蒼蘭香墨 我抬頭看了看天上的太陽。三九已至科贬,卻和暖如春泳梆,著一層夾襖步出監(jiān)牢的瞬間,已是汗流浹背榜掌。 一陣腳步聲響...
    開封第一講書人閱讀 31,961評論 1 265
  • 我被黑心中介騙來泰國打工优妙, 沒想到剛下飛機就差點兒被人妖公主榨干…… 1. 我叫王不留,地道東北人憎账。 一個月前我還...
    沈念sama閱讀 46,297評論 2 360
  • 正文 我出身青樓套硼,卻偏偏與公主長得像,于是被迫代替她去往敵國和親胞皱。 傳聞我的和親對象是個殘疾皇子邪意,可洞房花燭夜當晚...
    茶點故事閱讀 43,472評論 2 348