简体   繁体   English

WSO2 API管理器可能存在代理问题

[英]Possible proxy issue with WSO2 API Manager

Whenever I try to add the following endpoint, " http://ws.cdyne.com/phoneverify/phoneverify.asmx ", during the Managed API setup process and press the Test button I get an error on the server. 每当我在托管API设置过程中尝试添加以下终结点“ http://ws.cdyne.com/phoneverify/phoneverify.asmx ”并按“测试”按钮时,服务器上都会出现错误。 ERROR - APIProviderHostObject Error occurred while connecting to backend : "stackOverflow preventing me from showing this link", reason: Connect to ws.cdyne.com:80 timed out 错误-连接到后端时发生APIProviderHostObject错误:“ stackOverflow阻止我显示此链接”,原因:连接到ws.cdyne.com:80超时

When I try this exact same process on a machine outside of our proxy it works fine. 当我在代理服务器以外的计算机上尝试完全相同的过程时,它工作正常。 I have gone into the axis2.xml file and added proxy information and even went as far as installing cntlm and setting the proxy to localhost - same error. 我进入axis2.xml文件并添加了代理信息,甚至还安装了cntlm并将代理设置为localhost-同样的错误。

I can browse to the above link just fine on this machine. 我可以在这台机器上浏览到上面的链接。

My environment is Windows 10. 我的环境是Windows 10。

I assume you talk about clicking the Test button when providing Backend Endpoint in API publisher. 我假设您谈论在API Publisher中提供后端端点时单击“测试”按钮的问题。

The way that Test button works at the moment (as far as I understand) is that it invokes HTTP HEAD method on the endpoint provided (because according to RFC 2616 , " This method is often used for testing hypertext links for validity, accessibility, and recent modification. ") 目前,据我所知,“测试”按钮的工作方式是,它在提供的端点上调用HTTP HEAD方法(因为根据RFC 2616 ,“ 该方法通常用于测试超文本链接的有效性,可访问性和最近修改。 ”)

Then it checks response. 然后它检查响应。 If response is valid or 405 (method not allowed), then the URL is marked as Valid. 如果响应有效或为405(不允许使用方法),则该URL被标记为有效。

Thus sometimes, if backend is not properly following RFC, you might get otherwise working URLs declared as Invalid during the test because of that improper HEAD response evaluation. 因此,有时,如果后端未正确遵循RFC,则由于HEAD响应评估不正确,您可能会在测试期间获得其他无效的有效URL。 Obviously, this is just a check for your convenience and you can ignore the check if you know the endpoint works for the methods and resources you need it to work. 显然,这只是为了您的方便而进行的检查,如果您知道端点适用于您需要它的方法和资源,则可以忽略该检查。

So my advice would be to try ignoring the Test and just finishing setting up and publishing the API. 因此,我的建议是尝试忽略测试,而仅完成设置和发布API。

PS I am checking it on WSO2 API Cloud but behavior is identical to downloadable API Manager. PS我正在WSO2 API Cloud上对其进行检查,但行为与可下载的API Manager相同。

声明:本站的技术帖子网页,遵循CC BY-SA 4.0协议,如果您需要转载,请注明本站网址或者原文地址。任何问题请咨询:yoyou2525@163.com.

 
粤ICP备18138465号  © 2020-2024 STACKOOM.COM