Using for example getip for 186.140.179.34 returns the following data:
00000000 48 54 54 50 2f 31 2e 31 20 32 30 30 20 4f 4b 0d |HTTP/1.1 200 OK.|
00000010 0a 41 63 63 65 73 73 2d 43 6f 6e 74 72 6f 6c 2d |.Access-Control-|
00000020 41 6c 6c 6f 77 2d 4f 72 69 67 69 6e 3a 20 2a 0d |Allow-Origin: *.|
00000030 0a 43 61 63 68 65 2d 43 6f 6e 74 72 6f 6c 3a 20 |.Cache-Control: |
00000040 6e 6f 2d 63 61 63 68 65 0d 0a 43 6f 6e 74 65 6e |no-cache…Conten|
00000050 74 2d 54 79 70 65 3a 20 61 70 70 6c 69 63 61 74 |t-Type: applicat|
00000060 69 6f 6e 2f 6a 73 6f 6e 3b 20 63 68 61 72 73 65 |ion/json; charse|
00000070 74 3d 75 74 66 2d 38 0d 0a 44 61 74 65 3a 20 4d |t=utf-8…Date: M|
00000080 6f 6e 2c 20 31 36 20 4e 6f 76 20 32 30 31 35 20 |on, 16 Nov 2015 |
00000090 31 34 3a 34 38 3a 32 33 20 47 4d 54 0d 0a 53 65 |14:48:23 GMT…Se|
000000a0 72 76 65 72 3a 20 4d 61 73 68 61 70 65 2f 35 2e |rver: Mashape/5.|
000000b0 30 2e 36 0d 0a 58 2d 52 61 74 65 4c 69 6d 69 74 |0.6…X-RateLimit|
000000c0 2d 72 65 71 75 65 73 74 73 2d 4c 69 6d 69 74 3a |-requests-Limit:|
000000d0 20 31 30 30 30 0d 0a 58 2d 52 61 74 65 4c 69 6d | 1000…X-RateLim|
000000e0 69 74 2d 72 65 71 75 65 73 74 73 2d 52 65 6d 61 |it-requests-Rema|
000000f0 69 6e 69 6e 67 3a 20 39 37 32 0d 0a 43 6f 6e 74 |ining: 972…Cont|
00000100 65 6e 74 2d 4c 65 6e 67 74 68 3a 20 34 32 33 0d |ent-Length: 423.|
00000110 0a 43 6f 6e 6e 65 63 74 69 6f 6e 3a 20 6b 65 65 |.Connection: kee|
00000120 70 2d 61 6c 69 76 65 0d 0a 0d 0a 67 65 74 67 65 |p-alive…getge|
00000130 6f 69 70 28 7b 22 6f 66 66 73 65 74 22 3a 22 2d |oip({“offset”:"-|
00000140 33 22 2c 22 6c 6f 6e 67 69 74 75 64 65 22 3a 2d |3",“longitude”😐
00000150 35 38 2e 33 38 31 36 2c 22 63 69 74 79 22 3a 22 |58.3816,“city”:"|
00000160 42 75 65 6e 6f 73 20 41 69 72 65 73 22 2c 22 74 |Buenos Aires",“t|
00000170 69 6d 65 7a 6f 6e 65 22 3a 22 41 6d 65 72 69 63 |imezone”:“Americ|
00000180 61 5c 2f 41 72 67 65 6e 74 69 6e 61 5c 2f 42 75 |a/Argentina/Bu|
00000190 65 6e 6f 73 5f 41 69 72 65 73 22 2c 22 6c 61 74 |enos_Aires”,“lat|
000001a0 69 74 75 64 65 22 3a 2d 33 34 2e 36 30 33 33 2c |itude”:-34.6033,|
000001b0 22 61 72 65 61 5f 63 6f 64 65 22 3a 22 30 22 2c |“area_code”:“0”,|
000001c0 22 72 65 67 69 6f 6e 22 3a 22 44 69 73 74 72 69 |“region”:“Distri|
000001d0 74 6f 20 46 65 64 65 72 61 6c 22 2c 22 64 6d 61 |to Federal”,“dma|
000001e0 5f 63 6f 64 65 22 3a 22 30 22 2c 22 6f 72 67 61 |code":“0”,“orga|
000001f0 6e 69 7a 61 74 69 6f 6e 22 3a 22 41 53 31 31 33 |nization”:“AS113|
00000200 31 35 20 54 65 6c 65 66 f3 6e 69 63 61 20 4d f3 |15 Telef.nica M.|
00000210 76 69 6c 65 73 20 41 72 67 65 6e 74 69 6e 61 20 |viles Argentina |
00000220 53 2e 41 2e 20 28 4d 6f 76 69 73 74 61 72 20 41 |S.A. (Movistar A|
00000230 72 67 65 6e 74 69 6e 61 29 22 2c 22 63 6f 75 6e |rgentina)”,“coun|
00000240 74 72 79 22 3a 22 41 72 67 65 6e 74 69 6e 61 22 |try”:“Argentina”|
00000250 2c 22 69 70 22 3a 22 31 38 36 2e 31 34 30 2e 31 |,“ip”:“186.140.1|
00000260 37 39 2e 33 34 22 2c 22 63 6f 75 6e 74 72 79 5f |79.34”,"country|
00000270 63 6f 64 65 33 22 3a 22 41 52 47 22 2c 22 70 6f |code3”:“ARG”,“po|
00000280 73 74 61 6c 5f 63 6f 64 65 22 3a 22 31 38 37 31 |stal_code”:“1871|
00000290 22 2c 22 63 6f 6e 74 69 6e 65 6e 74 5f 63 6f 64 |”,“continent_cod|
000002a0 65 22 3a 22 53 41 22 2c 22 63 6f 75 6e 74 72 79 |e”:“SA”,“country|
000002b0 5f 63 6f 64 65 22 3a 22 41 52 22 2c 22 72 65 67 |_code”:“AR”,“reg|
000002c0 69 6f 6e 5f 63 6f 64 65 22 3a 22 30 37 22 7d 29 |ion_code”:“07”})|
000002d0 3b 0a |;.|
with the charset set to utf-8, but it seems like it’s returning UTF-16, for example the U00f3 glyph should be encoded as c3b3 in UTF-8 and not just f3 as in
the returned content.
====
00000200 31 35 20 54 65 6c 65 66 f3 6e 69 63 61 20 4d f3 |15 Telef.nica M.|
f3 should be c3b3 to be utf-8.
Join in the discussion - add comment below:
Hello again,
Indeed, there was a regression causing the organization name to be incorrectly encoded, this has just been fixed. City and region names were not affected.
Thanks again for reporting the issue!
Hello,
Thanks for reporting the issue, I will investigate.
Did it start happening after the switch to Mashape or did it already happen on the http://www.telize.com/geoip endpoint?
Regards.