receptor api returns InvalidJSON error for DesiredLRPUpdateRequest

[shalako]

I'm trying to update the routes field for an LRP.

$ curl receptor.10.244.0.34.xip.io/v1/desired_lrps/scoen-1 -X PUT -d '{"routes":{"tcp-router":[{"external_port":70000,"container_port":6379}]}}'
{"name":"InvalidJSON","message":"EOF"}

I have verified that this is valid JSON.

{  
    "routes":{  
        "tcp-router":[  
            {  
                "external_port":50001,
                "container_port":6379
            }
        ]
    }
}

@amitkgupta suggested something about the payload needs to be escaped; I have not found this documented.

[cf-gitbot]

We have created an issue in Pivotal Tracker to manage this. You can view the current status of your issue at: https://www.pivotaltracker.com/story/show/99277286.

[emalm]

Hi, @shalako,

Can you see if your request works with a -H 'Content-Type: application/json' flag added to your curl command? It works for me with that header.

I was getting the same errors you were without it, and verbose logging on the curl command showed it was sending a 'Content-Type: application/x-www-form-urlencoded' header with the PUT request.

Thanks,
Eric

[shalako]

Thank you, @ematpl . Using -H 'Content-Type: application/json' resulted in a success. Two points:

• Why is this necessary for update and not create?
• Consider documenting this gotcha in the DesiredLRPUpdateRequest API doc?

[emalm]

After some inspection of the receptor codebase down to the Golang net/http standard library package, it's not clear to me why the receptor endpoints fail to process a PUT payload correctly when a Content-Type: application/x-www-form-urlencoded header is on the request. I've created a story in the Diego tracker to investigate and in the meantime added a note about this behavior to the Task and LRP API references in the receptor docs.

Thanks,
Eric