848257 - Phonebook :: API :: Looks like API does not fetch the result when there is a white space in a given parameter.

Status: VERIFIED FIXED

(Participation Infrastructure :: Phonebook, defect)

Description

[ravi]

User Agent: Mozilla/5.0 (X11; Linux i686) AppleWebKit/537.17 (KHTML, like Gecko) Chrome/24.0.1312.56 Safari/537.17

Steps to reproduce:

prerequisite:

a) Find the profile which has data including a white space.
ex: Matt Brandt profile has 'Mountain View' for city.

Steps
--------
1. Hit the API request with these arguments -- https://mozillians.allizom.org/api/v1/users/?app_name=mozapp&app_key=test&city=Mountain View
2. Observe for the response.



Actual results:

1. The response code was 200. The result had nothing in it.


Expected results:

1. API to convert the white space character to respective code and fetch the result.

Comment 1

[ravi]

Test Investigation 
1. Looks like the white space in city is not considered.
2. May be replacing the white space with its HTTP character code might fetch the result. This is not tested.

Comment 2

[Giorgos Logiotatidis [:giorgos]]

Reproduced. Thanks for reporting, Ravi.

Comment 3

[Giorgos Logiotatidis [:giorgos]]

Commit pushed to master at https://github.com/mozilla/mozillians

https://github.com/mozilla/mozillians/commit/a814dc7f4b5a7157d6514ee0ced0e2e0f5fb63d9
[fix bug 911980][fix bug 848256][fix bug 848257] API refactoring, tests and bug fixing.

* Refactor API to not use the ElasticSearch backend (bug 911980)
* Explicitly set the fields returned by UserResource
* Fix filters containing spaces (bug 848257)
* Fix filters with commas (bug 848256)
* Fix default data ordering (bug 914384)

Comment 4

[William Reynolds [:williamr]]

Verified this is working on stage.