Project cross-domain agents often time out during vue-cli development. What are the possible reasons?

recently a vue project developed with a proxy set in proxyTable . It is quite normal to use it in the early stage, but I don"t know why there is an occasional connection timeout (the frequency is about 1max 20, which is estimated to be the efficiency of background response and network problems).
then timeout frequency is getting higher and higher , about 1 strong 5, but when another machine is used, the frequency of timeout is very small.
later, the router was changed and the computer was reinstalled with a network drive, but there was no improvement (there was a lot of slip on the external network). The worst nightmare of
is that no changes have been made to the project code these days, and every proxy request has timed out. Try to use native as the server , so if you use vue-cli to develop, you will still every proxy request will time out . While packaged items are normal, timeouts are rare .

recently, I didn"t give up. Reinstalling the network drive, restarting the computer, fully scanning, reinstalling the development environment, and upgrading the nodejs version (8.12.0) still did not solve the problem, but also pulled out a new problem. node-sass failed to install, tried rebuild, tried to delete dependencies and reinstalled, and tried partial installation without any effect.
I. It should still be able to save

.

through your description, there seems to be a myriad of possibilities for timeouts. First of all, you have to determine where there is no problem.
for example, it is OK to use tools such as curl/postman to test direct access to the background, and then open Network to see which part of the Timing is slow.


has not encountered a timeout, so infer it according to the description of the subject.

  1. Native server, there is also a timeout, that is, the proxy request is not sent to the server.
  2. the packaged project is normal, which means the service interface is fine.

guess where the problem may occur based on the above two points:

  1. dev and prod's api url do not use the same set, which may mean that dev's url has been mistakenly modified. Caused not to enter the API.
  2. The port of
  3. dev is blocked by the server.

suggestion:

  1. troubleshooting it is the above two problems that caused the connection timeout.
  2. debug proxy
Menu