Getting UnsupportedHeader code while trying to upload artifact

[divyanshu2601]

Describe the bug
Getting UnsupportedHeader code while trying to upload artifact

To Reproduce
Steps to reproduce the behavior:

1. We noticed UnsupportedHeader error coming in x-ms-error-code in version 2.1.8 @action/artifact

2. We upgraded @actions/artifact to 2.2.0 in our package.json

3. We have made call to uploadArtifact(artifactName, files, root directory, {retentionDays} of DefaultArtifactClient of @actions/artifact from our js file.

4. We observed below behaviour:
   upload-artifact.js makes call to uploadZipToBlobStorage under blob-upload.js where it makes a call to uploadStream method present in storage-blob and error occurs at uploadStream method where error says : RestError: One of the HTTP headers specified in the request is not supported.

5. When we look at the request header it is as below :
   

Expected behavior
Requested Artifact Should get uploaded to workflow .

Screenshots
Attached request header in point 5 above.

Response header looks like below :

Additional context
My first guess would be if x-ms-version 2025-01-05 is able to support the header being passed from @action/artifact ?

[akshaykhante]

I am also facing this issue. We do not set any headers while calling uploadArtifact method. It started failing after v2.2.0 release. Any breaking changes were released?
@yacaovsnc @bdehamer @robherley any help would be appreciated.

[yacaovsnc]

👋🏼 @akshaykhante @divyanshu2601 could you please repro the issue and give me the x-ms-client-request-id in the response again?

[akshaykhante]

@yacaovsnc It is ‘09c3bb65-ffab-4a46-b63a-47a18dcb451e’

[yacaovsnc]

@akshaykhante thanks. I also need the blob you are trying to upload to narrow down the query - I need the Azure Blob server name as well. Could you please show us the entire http call the script is trying to make?