AnsweredAssumed Answered

500 Internal Server Error - when uploading config payload to PAPI

Question asked by B-3-WECOPT Employee on Dec 8, 2015
Latest reply on Dec 11, 2015 by Jon Landis

Hi team,


I'm playing around with PAPI and trying to do something very simple: all I’m doing is pulling down the JSON payload for a config, changing the TTL (to 15 days) and pushing it back out (using PUT). The GET command works just fine, but after manipulating the config JSON and making a PUT request I get an error.


500 Internal Server Error


I set the my client to spit out Debug info. Here it is, with some of the auth headers/paths modified (for security reasons):


* Hostname was found in DNS cache * Trying * Connected to ( port 443 (#0) * Cipher selection: ALL:!EXPORT:!EXPORT40:!EXPORT56:!aNULL:!LOW:!RC4:@STRENGTH * SSL connection using TLSv1.0 / AES128-SHA * Server certificate: * subject: C=US; ST=MA; L=Cambridge; O=Akamai Technologies Inc.; OU=Edge Services; CN=* * start date: 2015-10-15 20:40:16 GMT * expire date: 2016-10-15 20:40:15 GMT * subjectAltName: matched * issuer: C=NL; L=Amsterdam; O=Verizon Enterprise Solutions; OU=Cybertrust; CN=Verizon Akamai SureServer CA G14-SHA2 * SSL certificate verify ok. > PUT /papi/v0/properties/prp_12345/versions/10/rules/?contractId=ctr_1-ABCD&groupId=grp_4321 HTTP/1.1 Host: User-Agent: Akamai-Open-Edgegrid-PHP/0.4.3 GuzzleHttp/6.1.0 curl/7.43.0 PHP/5.6.10 Content-Type: application/vnd.akamai.papirules.latest+json Authorization: EG1-HMAC-SHA256 client_token=akab-t36za4qjwsgg2fir;access_token=akab-rpon2gs2n76p7cik;timestamp=20151208T16:32:59+0000;nonce=5c03b849e5eddd69c440;signature=0UyVoayO2CiucV4WJok3tmH0fXI8= Content-Length: 6581 * upload completely sent off: 6581 out of 6581 bytes < HTTP/1.1 500 Internal Server Error < Server: Apache-Coyote/1.1 < Content-Language: en < Vary: Accept-Language,Accept < Content-Type: application/problem+json;charset=UTF-8 < Date: Tue, 08 Dec 2015 16:33:50 GMT < Transfer-Encoding: chunked < Connection: close < Connection: Transfer-Encoding < * Closing connection 0


What could be going wrong? What else can I provide to help debug this?

Once again, my GET request works perfectly fine so I know I'm using the client (auth headers) correctly.