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?

[akshaykhante]

@yacaovsnc sharing entire blob would not be possible. The size of blob is 25.2 mb.
Server is Windows-Azure-Blob/1.0 Microsoft-HTTPAPI/2.0
Also response gives error as Unsupportedheader and headerName as Transfer-Encoding.

Below is the part of script where i am calling uploadArtifact

const artifactClient = new DefaultArtifactClient();
.
.
const response = artifactClient.uploadArtifact(
    artifactName,
    filesToUpload,
    rootDir,
    { retentionDays: 90 }
);

where filesToUpload is a list of one or more files.

[yacaovsnc]

I don't mean the actual blob file - I mean the http call to upload the blob.

So if you enable debug log, you should see a [Request] CreateArtifact call, and the response on that call has a signed_upload_url in the format of: https://productionresultssa12.blob.core.windows.net/...

Can you please let me know both this blob server url and your request id?

[akshaykhante]

https://productionresultssa11.blob.core.windows.net/actions-results/0c395e52-b1bf-41cb-b8b9-750807593ed5/workflow-job-run-72319b38-cf22-5b97-6a85-18b068e18d5d/artifacts/1077131b727db735712883c4bc2b17f9f90e63023ed82a9db59a21bb6c3e58bd.zip?se=2025-01-28T19%3A55%3A33Z&sig=Qek0nxyCE7ee77V8%2FgndGq1VtjXteBVXR3O2CwC%2FEV8%3D&ske=2025-01-29T06%3A35%3A42Z&skoid=ca7593d4-ee42-46cd-af88-8b886a2f84eb&sks=b&skt=2025-01-28T18%3A35%3A42Z&sktid=398a6654-997b-47e9-b12b-9515b896b4de&skv=2024-11-04&sp=cw&spr=https&sr=b&st=2025-01-28T18%3A55%3A28Z&sv=2024-11-04

Request id : 399f10b1-301e-00db-7430-735eb9000000

[akshaykhante]

@yacaovsnc did you get anything?

[yacaovsnc]

@akshaykhante

Apologies I missed the message without an explicit mention. 🙇‍♂

Yeah I see your request, and from a glance, this header value doesn't seem right?

ContentLengthHeader: -1

[akshaykhante]

@yacaovsnc Thanks for the update. How the value of this header is picked as we are not setting any value explicitly? What should be the correct value?

Does this mean the files are not getting considered? Could you please provide more information?

[akshaykhante]

@yacaovsnc @bdehamer Bump on this issue.

Also the error was not helpful to determine which header is not supported. So if unsupportedheader error message can be improved it would help teams determine such issues by themselves.

[yacaovsnc]

@akshaykhante unfortunately I can only tell what happened on server side, actions/upload-artifact serves as reference implementation for the client. I am not able to debug client side implementations. I would hook up a debugger and step through the client to see why a negative value was generated. Could it be one of the file input to the uploadArtifact function is wrong? Or it maybe a dependency issue of some node packages?

[akshaykhante]

@yacaovsnc I was looking into debug logs of the signed_upload_url i shared. I noticed it have following headers:
Headers: {
“content-length”: “582”,
“content-type”: “application/json”,
//other fields like date, x-github-backend and x-github-request-id
}

Now wondering if the content-length was set to 582 in header, why it is ContentLengthHeader: -1 on server side?

[yacaovsnc]

@akshaykhante that call has a content-type of application/json - is it the call to create artifact? The -1 content length was seen on the call to upload the blobs.

There are three calls:

1. Create artifact, and the server should return you a SAS url
2. Make a zip stream from the file input, and stream the artifact to Azure Blob Storage
3. Finalize artifact creation.

I suspect the log you saw is from 1), and the -1 is from 2).

Usually, 2) should be hidden from caller, but file input and package dependencies may affect it. That's the part I don't have visibility to.