.NET Core 2.2项目能否通过方法调用直接调用内部HTTP端点？

当然可以！你完全不需要通过HttpClient发起实际HTTP请求，就能在同一项目内直接触发控制器的HTTP处理器——这正好能满足你用SignalR Hub复用现有API端点、实现类似feathers.js功能的需求。下面给你两种实用方案，根据你的场景选就行：

方案一：直接调用控制器方法（轻量版） #

如果你的控制器逻辑和HTTP上下文（比如User、Request.Headers）耦合度不高，直接实例化控制器并调用对应方法是最简洁的方式。关键是利用依赖注入容器解析控制器的依赖。

示例代码 #

首先是你的API控制器：

[Route("api/[controller]")]
[ApiController]
public class ThingsController : ControllerBase
{
    private readonly IThingService _thingService;

    // 依赖注入业务服务
    public ThingsController(IThingService thingService)
    {
        _thingService = thingService;
    }

    [HttpPost]
    public async Task<IActionResult> CreateThing([FromBody] ThingDto dto)
    {
        var newThing = await _thingService.CreateAsync(dto);
        return CreatedAtAction(nameof(GetThing), new { id = newThing.Id }, newThing);
    }

    [HttpGet("{id}")]
    public async Task<IActionResult> GetThing(int id)
    {
        var thing = await _thingService.GetByIdAsync(id);
        return thing == null ? NotFound() : Ok(thing);
    }
}

然后是实现复用逻辑的SignalR Hub：

public class RealtimeHub : Hub
{
    private readonly IServiceProvider _serviceProvider;

    public RealtimeHub(IServiceProvider serviceProvider)
    {
        _serviceProvider = serviceProvider;
    }

    // 对应客户端调用的"POST"方法
    public async Task<object> InvokeApi(string method, string path, string jsonBody)
    {
        // 这里简化路径匹配，你可以扩展成更通用的路由解析逻辑
        if (path.Equals("/api/things", StringComparison.OrdinalIgnoreCase))
        {
            // 创建服务作用域，确保控制器依赖正确释放
            using var scope = _serviceProvider.CreateScope();
            var thingsController = scope.ServiceProvider.GetRequiredService<ThingsController>();

            switch (method.ToUpper())
            {
                case "POST":
                    var dto = JsonConvert.DeserializeObject<ThingDto>(jsonBody);
                    var createResult = await thingsController.CreateThing(dto);
                    return ConvertActionResultToClientResponse(createResult);
                case "GET":
                    // 处理GET请求，解析路径中的id参数
                    var id = int.Parse(path.Split('/').Last());
                    var getResult = await thingsController.GetThing(id);
                    return ConvertActionResultToClientResponse(getResult);
                // 扩展PUT、DELETE等其他方法
                default:
                    throw new ArgumentException($"Unsupported HTTP method: {method}");
            }
        }

        throw new InvalidOperationException($"No API endpoint found for path: {path}");
    }

    // 把IActionResult转换成客户端能识别的结构化响应
    private object ConvertActionResultToClientResponse(IActionResult result)
    {
        return result switch
        {
            OkObjectResult ok => new { StatusCode = ok.StatusCode, Data = ok.Value },
            CreatedAtActionResult created => new { StatusCode = created.StatusCode, Data = created.Value },
            NotFoundResult notFound => new { StatusCode = notFound.StatusCode },
            BadRequestObjectResult badReq => new { StatusCode = badReq.StatusCode, Error = badReq.Value },
            _ => new { StatusCode = 500, Error = "Unknown response type" }
        };
    }
}

方案二：模拟完整HTTP请求管道（完整版） #

如果你的控制器依赖HTTP上下文、需要触发模型验证、过滤器（Authorization/Action Filter）等完整ASP.NET Core管道功能，就可以通过模拟HTTP请求来调用控制器。

示例代码 #

public class RealtimeHub : Hub
{
    private readonly IHttpContextAccessor _httpContextAccessor;
    private readonly IActionInvokerFactory _actionInvokerFactory;
    private readonly IActionSelector _actionSelector;
    private readonly IServiceProvider _serviceProvider;

    public RealtimeHub(IHttpContextAccessor httpContextAccessor, 
                       IActionInvokerFactory actionInvokerFactory,
                       IActionSelector actionSelector,
                       IServiceProvider serviceProvider)
    {
        _httpContextAccessor = httpContextAccessor;
        _actionInvokerFactory = actionInvokerFactory;
        _actionSelector = actionSelector;
        _serviceProvider = serviceProvider;
    }

    public async Task<object> InvokeApi(string method, string path, string jsonBody)
    {
        // 创建全新的HttpContext
        var httpContext = new DefaultHttpContext
        {
            RequestServices = _serviceProvider.CreateScope().ServiceProvider
        };

        // 配置请求参数
        httpContext.Request.Method = method;
        httpContext.Request.Path = path;
        httpContext.Request.ContentType = "application/json";
        
        // 写入请求体
        using var requestStream = new MemoryStream(Encoding.UTF8.GetBytes(jsonBody));
        httpContext.Request.Body = requestStream;

        // 匹配对应的Action端点
        var actionContext = new ActionContext(httpContext, new RouteData(), new ControllerActionDescriptor());
        var actionCandidates = _actionSelector.SelectCandidates(actionContext);
        var selectedAction = _actionSelector.SelectBestCandidate(actionContext, actionCandidates);

        if (selectedAction == null)
        {
            return new { StatusCode = 404, Error = $"No action found for {method} {path}" };
        }

        actionContext.ActionDescriptor = selectedAction;

        // 执行完整的Action管道
        var invoker = _actionInvokerFactory.CreateInvoker(actionContext);
        await invoker.InvokeAsync();

        // 读取响应结果
        httpContext.Response.Body.Seek(0, SeekOrigin.Begin);
        var responseBody = await new StreamReader(httpContext.Response.Body).ReadToEndAsync();

        return new { 
            StatusCode = httpContext.Response.StatusCode, 
            ResponseBody = responseBody 
        };
    }
}

注意事项 #

• 方案一适合业务逻辑独立的场景，性能更高；方案二适合需要完整HTTP管道特性的场景，更贴近真实请求；
• 确保在Startup.cs中注册了必要服务：services.AddHttpContextAccessor()、services.AddControllers()、services.AddSignalR()；
• 你的客户端SignalR调用代码完全可以直接使用，只需要确保Hub的方法名和参数对应即可。

内容的提问来源于stack exchange，提问作者bbrownd