AnsweredAssumed Answered

"Signature does not match" Error When Posting Fast DNS Zone >256KB

Question asked by Warron Lunde on Mar 5, 2015
Latest reply on Mar 10, 2015 by Laurence Leccia

I need to add several hundred co-branding records to an existing Fast DNS primary zone. Once I had the syntax of my PowerShell script correct, I was able to successfully add dozens of test records. When I tried to add 700+ records that I need to add for this zone, the API started returning the following error:


Invoke-RestMethod : { "type": "", "title": "Not authorized", "status": 401, "detail": "The signature

does not match", "instance": "", "method": "POST",

"serverIp": "", "clientIp": "", "requestId": "13655de", "requestTime": "2015-03-05T06:42:25Z" }

At C:\Scripts\Invoke-AkamaiOPEN.ps1:144 char:2

+     Invoke-RestMethod -Method $Method -WebSession $api -Uri $ReqURL -Headers $Heade ...

+    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

    + CategoryInfo          : InvalidOperation: (System.Net.HttpWebRequest:HttpWebRequest) [Invoke-RestMethod], WebException

    + FullyQualifiedErrorId : WebCmdletWebResponseException,Microsoft.PowerShell.Commands.InvokeRestMethodCommand


After a lot of experimentation, I determined that this error is thrown when the body of the post exceeds 256 KB. Is this an arbitrary limit imposed on the API or is there an inherent limitation somewhere? If it's arbitrary, can we please increase this limit to a considerably higher? The body I am looking to post is 631 KB, so 256 KB doesn't even get me halfway there.