Removing custom handler request forwarding configuration

[fabiocav]

Removing the custom handler request forwarding configuration to avoid confusion.

Purpose

• ...
  This pull request makes a minor configuration update to the host.json file, changing the HTTP request handling setting. The enableForwardingHttpRequest property has been removed and replaced with enableHttpProxyingRequest.

Does this introduce a breaking change?

[ ] Yes
[x] No

Pull Request Type

What kind of change does this Pull Request introduce?

[ ] Bugfix
[ ] Feature
[ ] Code style update (formatting, local variables)
[x] Refactoring (no functional changes, no api changes)
[ ] Documentation content changes
[ ] Other... Please describe:

Other Information

[justinyoo]

Without this property, enableForwardingHttpRequest, this MCP server is not captured by GHCP agent mode. It should not be removed.

[lilyjma]

@fabiocav - is this a change that would require the new version of the host?

[fabiocav]

This change requires the latest version of the host and Core Tools. Those are already fully deployed, so you should be able to merge this.

Without this property, enableForwardingHttpRequest, this MCP server is not captured by GHCP agent mode. It should not be removed.

This is likely because your validation was done with an older version of the tool and proxying was not working (as it wasn't a feature in the old versions), so it would fallback to forwarding, which is not something we want to do.

[lilyjma]

Tested. Needs latests Azure Functions Core Tools (v.4.2.1) to work without the setting.