abpframework / abpframework/abp

Automatically set HttpClient.BaseUrl when the HttpClient name matches to a remote service name

Open
#12,690 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

abp-framework breaking change feature
Dominant language
C#
Stars
14.4k
Forks
3.7k
Avg merge
15h 32m
Merged PRs (30d)
106

Description

When we use IHttpClientFactory to obtain a named HttpClient, we can automatically set its BaseUrl by getting the value from the remote service configuration (IRemoteServiceConfigurationProvider). We should be sure that this won't be a breaking change for ABP Framework or client applications. If so, we may provide a way to use the old behavior.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Locate the IHttpClientFactory integration and IRemoteServiceConfigurationProvider implementation, then trace how named clients and remote service configurations are currently resolved. Define completion as matching names setting HttpClient.BaseUrl without breaking existing ABP Framework or client behavior, including a documented compatibility path if needed.

Written by the indexing model from the issue text.

Assessment

Tech stack
csharp
Domain
backend-api-design
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.