-
Notifications
You must be signed in to change notification settings - Fork 31
Closed
Description
We have been getting bad request errors for Invoke-AzsAzureBridgeProductDownload and Remove-AzsAzureBridgeDownloadedProduct. The error looks like the following:
FINALLY Response: 'StatusCode: 400, ReasonPhrase: 'Bad Request', Version: 1.1, Content: System.Net.Http.HttpConnectionResponseContent, Headers:
{
Server: Microsoft-HTTPAPI/2.0
Date: Thu, 16 Jul 2020 04:25:53 GMT
Connection: close
Content-Type: text/html; charset=us-ascii
Content-Length: 346
}'
FINALLY Value: '0'
VERBOSE: INFORMATION: FINALLY ExtendedData Type: ''
FINALLY ExtendedData ''
DEBUG: Finally:
Remove-AzsAzureBridgeDownloadedProduct_Delete: The server responded with a Request Error, Status: BadRequest
The issue is caused by appending of request headers from previous requests to the new request until the size of the request header is too large and it becomes a bad request.
Metadata
Metadata
Assignees
Labels
No labels