-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi,
yes, using the API URL in a browser would cause "Bad Request" because the API requires the extra header : Ddr-User-Agent, as described in the documentation. The idea is that the API responds to a request to resolve "a" user-agent string supplied in parameter [the Ddr-User-Agent http header] and not the user-agent string of the device calling the API ;-) [on Skype now] esjr -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.8 (MingW32) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQEcBAEBAgAGBQJTLgIIAAoJEOxywXcFLKYcuscH/0YyJ6/hz/HWge+bVT6uPUmN G+aYOXc9GKZqtMqMISOahVw024ZzMBjCP6XspdNycvQJ2UpxHCvU8oa2GGfvr14U BW8vRxUpxP67aX5EzUdH972wPNDJriNfNiqd6w7BCjkuQpuCe7qpCpubm0ZzY5/0 QpB1hbRbkLELhuPHaTz/x7Y0gaKGHwYo/E5oFi7giFW1ttivE7oqZ8HyMviGKANb WPlOM+mve9PkfzQwc0frc9y9N2Wb7DHM/rTk7rlbGtpLqJbG/trrurcXQKCj9pGi 4NlXuBqPjszjtU8HhAz/s7B2TfsLYEwmhsVz26S9QlGdlamg7ESWAYCtB28L7QI= =RJSQ -----END PGP SIGNATURE-----
