[ 
https://issues.apache.org/jira/browse/STRATOS-1268?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14494269#comment-14494269
 ] 

Chamila de Alwis commented on STRATOS-1268:
-------------------------------------------

Fixed in d42e63efb600e4cdfcd6d9f3d7491534ed083242. Now returns 200 OK. 

> Two different status codes appear -  PUT /deploymentPolicies
> ------------------------------------------------------------
>
>                 Key: STRATOS-1268
>                 URL: https://issues.apache.org/jira/browse/STRATOS-1268
>             Project: Stratos
>          Issue Type: Sub-task
>          Components: REST API
>    Affects Versions: 4.1.0 Alpha
>            Reporter: Mariangela Hills
>            Assignee: Dinithi De SIlva
>
> When executing the cURL command related to PUT /deploymentPolicies REST API 
> resource, two different status codes (201 and 200) appears in the HTTP 
> output. However, normally the 200 HTTP status code should be returned when 
> updating. 
> # < HTTP/1.1 201 Created
> # {"statusCode":200,"successMessage":"Deployment policy updated successfully: 
> [deployment-policy-id] deployment-policy-1"}
> The status codes should be identical
> ---------
> > PUT /api/deploymentPolicies HTTP/1.1
> > Authorization: Basic YWRtaW46YWRtaW4=
> > User-Agent: curl/7.24.0 (x86_64-apple-darwin12.0) libcurl/7.24.0 
> > OpenSSL/0.9.8| zlib/1.2.5
> > Host: localhost:9443
> > Accept: */*
> > Content-Type: application/json
> > Content-Length: 281
> > 
> * upload completely sent off: 281 out of 281 bytes
> < HTTP/1.1 201 Created
> < Date: Thu, 19 Mar 2015 09:27:06 GMT
> < Location: https://localhost:9443/api/deploymentPolicies/deployment-policy-1
> < Content-Type: application/json
> < Transfer-Encoding: chunked
> < Server: WSO2 Carbon Server
> < 
> * Connection #0 to host localhost left intact
> {"statusCode":200,"successMessage":"Deployment policy updated successfully: 
> [deployment-policy-id] deployment-policy-1"}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to