stratos-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Mariangela Hills <mariang...@wso2.com>
Subject Re: [Improvement] Searching for cartridges with a filter - pass a message in the response message
Date Sat, 21 Mar 2015 02:43:05 GMT
+1 your suggestion makes complete sense. I have created JIRA [1], so that
this issue can be fixed.

[1] https://issues.apache.org/jira/browse/STRATOS-1275

Regards,
Mariangela




*--*
Mariangela Hills
Senior Technical Writer

*WSO2, Inc.*lean.enterprise.middleware.
m: +94 773 500185
w: http://wso2.com
<http://wso2.com/events/>

On Sat, Mar 21, 2015 at 7:22 AM, Chamila De Alwis <chamilad@wso2.com> wrote:

> Hi,
>
> Shouldn't we send a 404 status instead of a 200 since no resources are
> found with respect to this request?
>
> If we do that there would no need for a client to check if value is empty.
> On Mar 21, 2015 6:32 AM, "Mariangela Hills" <mariangela@wso2.com> wrote:
>
>> Hi Devs,
>>
>> When searching for cartridges with filters, if there are no search
>> results available for the respective search, a blank response message is
>> returned [1]. This was a bit misleading to me as a user. I feel that it
>> will be good to return a message such as, "Cartridges not found" in the
>> response message. Please let me know what you all think regarding this
>> suggestion.
>>
>> [1]
>> Admin16s-MacBook-Air:samples Admin16$ curl -X GET -H "Content-Type:
>> application/json" -k -v -u admin:admin
>> https://localhost:9443/api/cartridges/filter/multiTenant
>> * About to connect() to localhost port 9443 (#0)
>> *   Trying ::1...
>> * connected
>> * Connected to localhost (::1) port 9443 (#0)
>> * SSLv3, TLS handshake, Client hello (1):
>> * SSLv3, TLS handshake, Server hello (2):
>> * SSLv3, TLS handshake, CERT (11):
>> * SSLv3, TLS handshake, Server key exchange (12):
>> * SSLv3, TLS handshake, Server finished (14):
>> * SSLv3, TLS handshake, Client key exchange (16):
>> * SSLv3, TLS change cipher, Client hello (1):
>> * SSLv3, TLS handshake, Finished (20):
>> * SSLv3, TLS change cipher, Client hello (1):
>> * SSLv3, TLS handshake, Finished (20):
>> * SSL connection using DHE-RSA-AES256-SHA
>> * Server certificate:
>> *  subject: C=US; ST=CA; L=Mountain View; O=WSO2; CN=localhost
>> *  start date: 2010-02-19 07:02:26 GMT
>> *  expire date: 2035-02-13 07:02:26 GMT
>> *  common name: localhost (matched)
>> *  issuer: C=US; ST=CA; L=Mountain View; O=WSO2; CN=localhost
>> *  SSL certificate verify result: unable to get local issuer certificate
>> (20), continuing anyway.
>> * Server auth using Basic with user 'admin'
>> > GET /api/cartridges/filter/multiTenant 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
>> >
>> < HTTP/1.1 200 OK
>> < Date: Sat, 21 Mar 2015 00:45:12 GMT
>> < Content-Type: application/json
>> < Content-Length: 2
>> < Server: WSO2 Carbon Server
>> <
>> * Connection #0 to host localhost left intact
>> *[]** Closing connection #0
>> * SSLv3, TLS alert, Client hello (1):
>>
>>
>>
>> Regards,
>> Mariangela
>>
>>
>>
>>
>> *--*
>> Mariangela Hills
>> Senior Technical Writer
>>
>> *WSO2, Inc.*lean.enterprise.middleware.
>> w: http://wso2.com
>>
>>

Mime
View raw message