You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
Getting UnsupportedHeader code while trying to upload artifact
To Reproduce
Steps to reproduce the behavior:
We noticed UnsupportedHeader error coming in x-ms-error-code in version 2.1.8 @action/artifact
We upgraded @actions/artifact to 2.2.0 in our package.json
We have made call to uploadArtifact(artifactName, files, root directory, {retentionDays} of DefaultArtifactClient of @actions/artifact from our js file.
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.
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 ?
The text was updated successfully, but these errors were encountered:
Describe the bug
Getting UnsupportedHeader code while trying to upload artifact
To Reproduce
Steps to reproduce the behavior:
We noticed UnsupportedHeader error coming in x-ms-error-code in version 2.1.8 @action/artifact
We upgraded @actions/artifact to 2.2.0 in our package.json
We have made call to uploadArtifact(artifactName, files, root directory, {retentionDays} of DefaultArtifactClient of @actions/artifact from our js file.
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.
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 ?
The text was updated successfully, but these errors were encountered: