当API管理到逻辑应用时出现“404未找到”错误,通常是由于以下几种原因引起的:
以下是一个示例,演示了如何在逻辑应用中配置API连接:
{
"$connections": {
"value": {
"apiConnectionName": {
"connectionId": "/subscriptions/{subscription-id}/resourceGroups/{resource-group}/providers/Microsoft.Web/connections/{api-connection-name}",
"connectionName": "apiConnectionName",
"id": "/subscriptions/{subscription-id}/providers/Microsoft.Web/locations/{location}/managedApis/{api-name}",
"displayName": "API Connection Name",
"api": {
"id": "/subscriptions/{subscription-id}/providers/Microsoft.Web/locations/{location}/managedApis/{api-name}",
"displayName": "API Name",
"serviceUrl": "https://{api-url}",
"properties": {
"api": {
"id": "/subscriptions/{subscription-id}/providers/Microsoft.Web/locations/{location}/managedApis/{api-name}",
"displayName": "API Name",
"serviceUrl": "https://{api-url}",
"endpointUrl": "https://{api-url}",
"endpointBaseUrl": "https://{api-url}",
"connectionParameters": {
"apiName": "{api-name}"
}
}
}
}
}
}
}
}
以下是一个示例,演示了如何在API管理中配置API操作:
{
"swagger": "2.0",
"info": {
"title": "API Name",
"version": "1.0"
},
"host": "{api-url}",
"basePath": "/api",
"schemes": [
"https"
],
"paths": {
"/resource": {
"get": {
"operationId": "get-resource",
"parameters": [
{
"name": "id",
"in": "query",
"type": "string",
"required": true
}
],
"responses": {
"200": {
"description": "Success"
}
}
}
}
}
}
API管理中的API操作未正确发布:确认API操作是否已正确发布到API管理。检查API操作的状态和版本等信息。
访问的API不存在或不可用:验证API是否存在,并且可以通过提供的URL进行访问。确保API正在运行并且可以正常访问。
如果上述方法仍未解决问题,则可能需要进一步调试和排查。可以查看逻辑应用和API管理的日志,以获取更详细的错误信息,并尝试根据错误信息进行进一步的故障排除。
上一篇:API管理策略中的液体映射问题