Unanswered

Custom Connector sending additional headers - Ways to disable this?

(1) Share

Report

Posted on by AlexN

269

Hey everyone,

I stumbled over a little "gimmick" of custom connectors yesterday.

A customer is using Azure OpenAI in a private network. Since none of the existing OpenAI connectors support gateways, I just made a very simple Custom Connector to be able to select a gateway.

The only header values defined are api-key and Content-Type. When I test the connector in the connector editor, everything works fine.

Using the custom connector though behaves different. The answer I always get is Error 431 - Request header fields too large.
With the normal http-Connector, there is an option in the action settings to suppress sending workflow headers. For a custom connector, there isn't such an option. My guess is, there will be some of the typical "x-auth-..." headers, that Power Automate is adding on its own.

Is there any way I can restrict the connector from doing so? Don't want to setup an additional API Management in Azure just to strip the headers...

Categories:

Building flows

I have the same question (1)

All responses (3)

Answers (0)

AlexN 269 on at

Like (0)

Report

A little bump

Was this reply helpful? Yes No
Ramon Tebar 4 on at

Like (0)

Report

Hey @AlexN, you are not alone 😅 I'm getting the same issue here. Did you find out anything else?

I noticed it normally works with the completions endpoint, but it fails with the Chat completions endpoint.

Was this reply helpful? Yes No
GC-07020925-0 2 on at

Like (0)

Report

We're also getting a 431 when using a Custom connector, in our case when calling OpenAI (although strangely only for certain models).

Unfortunately we have to use this as we need to use Virtual Network integration and most connectors (including HTTP) don't support this.

We don't get the 431 when testing the connector, only when running it from a Cloud Flow. I've not been able to see the requests so far.

Was this reply helpful? Yes No