Hi!
It seems you specify the parameters twice: once in the URL and once in the parameter list.
So either
*) you specify them in the URL (without any parameter list), i.e.
Quote:http://api.zip-codes.com/ZipCodesAPI.svc/1.0/FindZipCodesInRadius?zipcode=23954&maximumradius=50&minimumradius=0&key=XXXXXXXXXXXX
*) or you specify the URL without parameters and declare them seperately:
Quote:http://api.zip-codes.com/ZipCodesAPI.svc/1.0/FindZipCodesInRadius
zipcode=23954
maximumradius=50
minimumradius=0
key=XXXXXXXXXXXX
This way, you should get a response from the server.
BUT: you will get parsing errors since the returned json contains a byte order mark (BOM) at the beginning of the response.
According to
https://tools.ietf.org/html/rfc8259#section-8.1 this is not allowed:
Quote:8.1. Character Encoding
JSON text exchanged between systems that are not part of a closed ecosystem MUST be encoded using UTF-8 [RFC3629].
Previous specifications of JSON have not required the use of UTF-8 when transmitting JSON text. However, the vast majority of JSON- based software implementations have chosen to use the UTF-8 encoding, to the extent that it is the only encoding that achieves interoperability.
Implementations MUST NOT add a byte order mark (U+FEFF) to the beginning of a networked-transmitted JSON text. In the interests of interoperability, implementations that parse JSON texts MAY ignore the presence of a byte order mark rather than treating it as an error.
We will try to find a workaround for this for the next version of MobileTogether, but maybe you want to ask the technician of Zip Codes, why they return a BOM, in the meantime!?
