reactjs – 当Azure上托管后端时,create-react-app代理请求失败,

"proxy":{
   "/api/*":{
   "target":"https://mytestbackend.azurewebsites.net","secure":false
}
}

我已经设置了一个axios请求,要求发送到azure上的后端服务器.它是一个独立的.js,我从我的一个反应应用程序的事件中调用它.它看起来像这样：

import axios from 'axios';

const login = async (username,password) => {
   console.log("Username to send is:"+username);
   console.log("password to send is:"+password);
   let response = await axios.post('/api/user/login',{username:username,password:password});
   console.log(response);
};

export {login};

问题不在我的反应组件中,因为这两个console.log()调用显示正在接收输入的值.如果我从package.json中删除“secure”：false设置,则请求失败并显示Http Error：500.但如果我使用安全设置,则会失败并显示404页面.有人可以说清楚我做错了什么吗？我可以只在“localhost”上使用代理吗？文档另有说明.任何帮助是极大的赞赏.

我已经验证在Azure管理门户上运行dev服务器的域上启用了CORS.如果我直接使用后端的URL(即不使用create-react-app代理)来执行请求,它就可以工作.问题必须是代理配置的方式.

不使用安全时发生的HTTP Errpr 500的响应文本是：

Proxy error: Could not proxy request /api/user/login from localhost:3000 to https://mytestbackend.azurewebsites.net (undefined).

附加信息：我还通过在我的开发机器上本地运行我的后端进行了测试.出现错误消息,但括号中的“未定义”表示“UNABLE_TO_VERIFY_LEAF_SIGNATURE”.如果使用“secure：false,我可以成功调用登录端点,但是对需要身份验证的其他端点的调用失败,因为axios不发送cookie.

这样做：
卷曲-v https://mytestbackend.azurewebsites.net/api/user/login

有这个输出：

* SSLv3,TLS handshake,Client hello (1):
* SSLv3,Server hello (2):
* SSLv3,CERT (11):
* SSLv3,TLS alert,Server hello (2):
* SSL certificate problem: unable to get local issuer certificate
* Closing connection #0
curl: (60) SSL certificate problem: unable to get local issuer certificate
More details here: http://curl.haxx.se/docs/sslcerts.html

curl performs SSL certificate verification by default,using a "bundle"
of Certificate Authority (CA) public keys (CA certs). If the default
bundle file isn't adequate,you can specify an alternate file
using the --cacert option.
If this HTTPS server uses a certificate signed by a CA represented in
the bundle,the certificate verification probably failed due to a
problem with the certificate (it might be expired,or the name might
not match the domain name in the URL).
If you'd like to turn off curl's verification of the certificate,use
the -k (or --insecure) option.