Error: Network Error in edge but perfect in chrome and the project after built is working in edge

[fionsay]

Hi,
I'm wondering why get the error in edge when using developing mode but perfect in chrome,
and the project after built (npm run build) is working in edge (so weird ).

Here is the code: 

axios.get(api_url, {....})
.then(()=>{
     // code...
}).catch((error)=>{
     // error.response war undefined
     console.log(error, error.response)
})

Here is the error:
Error: Network Error
at createError 
at handleError 

• axios version: ^0.16.2
• vue: ^2.3.3
• vue-router: ^2.3.1
• vuex: ^2.3.1

[yufengwang]

let me see see

[fionsay]

@yufengwang

stack "Error: Network Error
at createError  (eval code:16:3)
at handleError (eval code:87:7)"

I got the error when I ran the vue project by developing mode.
I thought maybe the edge don't allow localhost loopback for websockets, but it don't work even if enabling loopback.:(

[rubennorte]

That isn't likely a problem in Axios so can you please send this to Gitter or StackOverflow and provide enough information to understand what problem you are having? Thanks.

[Sigura]

That isn't likely a problem in Axios

no, it's. because requests through other libs like fetch work perfectly.

see the same problem in Edge (40) only, FF, Chrome work perfect.

other environment staff:

1. request with CORS support, localhost, ports differed
2. response body json, all headers correct

[iaminvictus1993]

mark, i meet the same problem, prod mode is good, but dev mode error

[darthmooguy]

I've got the same problem too! Using create-react-app with the webpack-dev server, the requests always fails with a "Network Error" in Edge, but not in other browsers. When I run the compiled "dist" version, eveything is fine.

[Orange-way]

I've got the same problem too! How do you solve it finally?

[ivanmem]

Такая же проблема, в разработке, а в проде норм.

[nadilas]

Same here

[Cnordbo]

Im getting the same problem on Edge when i am behind a proxy.

Response snapshot:

2 headers included (Authorization and accept)

Chrome works fine.

Turning off the proxy and vpn connection makes the error disappear for me.

[marco9446]

I have the same error described before. I'm not using any vpn or proxy. Do someone has any tips or idea on what should i do to fix this problem with Edge ?