Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

[FEEDBACK]: apiPort setting is not available in devproxyrc.json #1218

Discussion options

Type of issue

Outdated article

Feedback

The documentation mentions various proxy settings but does not include information about the apiPort setting in devproxyrc.json. It would be helpful to clarify if this setting is supported or intended to be configurable in devproxyrc.json. If not, please update the documentation to explicitly state its absence to avoid confusion.

Link to documentation: Proxy Settings - Microsoft Learn

Thank you for your attention!

Page URL

https://learn.microsoft.com/en-us/microsoft-cloud/dev/dev-proxy/technical-reference/proxy-settings

Content source URL

https://github.com/MicrosoftDocs/microsoft-cloud/blob/main/docs/dev/dev-proxy/technical-reference/proxy-settings.md

Author

@garrytrinder

Document Id

6004001f-4791-7ca2-9818-d788175f3f4b

You must be logged in to vote

If I specify apiPort in Dev Proxy config, it seems to be working just fine:

Could you please share with me your repro steps?

Replies: 6 comments

Comment options

Thank you for reaching out. apiPort is the first setting mentioned in the doc:

Image

Because it's included in this listing, it means that it can be configured in devproxyrc.json. Or am I misunderstanding your comment and you mean something else? 🙂

You must be logged in to vote
0 replies
Comment options

The apiPort is not available on the schema of the config file https://github.com/microsoft/dev-proxy/blob/main/schemas/v0.23.0/rc.schema.json, and when I was trying to set the apiPort in the config, devproxy was not working for me. Given these circumstances, I was confused whether the documentation needs to be updated.

You must be logged in to vote
0 replies
Comment options

Understood, thank you for clarifying. Let me verify it and I'll get back to you when I know more.

You must be logged in to vote
0 replies
Comment options

apiPort missing in the schema is a bug and we'll fix it asap

You must be logged in to vote
0 replies
Comment options

If I specify apiPort in Dev Proxy config, it seems to be working just fine:

Image

Could you please share with me your repro steps?

You must be logged in to vote
0 replies
Answer selected by waldekmastykarz
Comment options

Closing due to lack of response

You must be logged in to vote
0 replies
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
Q&A
Labels
None yet
Converted from issue

This discussion was converted from issue #942 on June 04, 2025 10:00.

AltStyle によって変換されたページ (->オリジナル) /