We're getting the 9001 error code randomly on this request:

http://api.7digital.com/1.2/artist/details?artistId=473615&oauth_cons...

This happens despite the previous three requests (which happen
directly before, with identical URLs but different artistId's), which
work fine. The request works fine on our local dev versions, but
errors on our live server.

Your API Docs mention that we should contact you when we get an error
code above 7000.

Any ideas on what might be causing this?

Aaron,

We just experienced a very brief outage with our loadbalancer setup, but
this has been fixed.

Please could you try again and let us know if you are still experiencing
problems.

Thanks,
Chris

On 19 April 2012 13:49, Aaron Somal <aaronso...@googlemail.com> wrote:

Unfortunately we're still experiencing this issue.

Aaron

Hello Aaron,

we're not able to replicate the bug, can you tell us if your dev has any
differences from live? Different keys, parameters, anything else?

Would be good to get some copies of the responses if possible, including
headers.

Thanks

On 19 April 2012 14:42, Aaron Somal <aaronso...@googlemail.com> wrote:

The only difference is that our dev version runs locally, while the
live server runs from a remote server. The request is sent in exactly
the same way with the same key and parameters.

The response code is:
<?xml version="1.0" encoding="utf-8" ?><response status="ok"
version="1.2"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:noNamespaceSchemaLocation="http://api.7digital.com/1.2/static/
7digitalAPI.xsd" ><artist id="473615"><name>Veronica Falls</
name><sortName>Veronica Falls</sortName><url>http://www.7digital.com/
artists/veronica-falls/?partner=1375</url><image>http://cdn.
7static.com/static/img/artistimages/00/004/736/0000473615_150.jpg</
image><bio><text></text></bio></artist></response>?<?xml version="1.0"
encoding="utf-8" ?>
 <response status="error" version="1.2">
 <error code="9001">
 <errorMessage>Unhandled 7digital API server error.</errorMessage>
 </error>
</response>

It seems that we get a legitimate response, but an error code is also
attached to it.

Aaron

Hey,
I haven't seen this behaviour before, can you curl the request? please send
us a manual request including headers.

We don't have more than one status code per response, are you merging or
threading requests in any way?

Thanks

On 19 April 2012 15:05, Aaron Somal <aaronso...@googlemail.com> wrote:

We've tried with a CURL request and this responds fine.

We've also noticed the earlier response contains 2 different XML
declarations:

Part 1 (correct response) -
<?xml version="1.0" encoding="utf-8" ?><response status="ok"
version="1.2"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:noNamespaceSchemaLocation="http://api.7digital.com/1.2/static/
7digitalAPI.xsd" ><artist id="473615"><name>Veronica Falls</
name><sortName>Veronica Falls</sortName><url>http://www.7digital.com/
artists/veronica-falls/?partner=1375</url><image>http://cdn.
7static.com/static/img/artistimages/00/004/736/0000473615_150.jpg</
image><bio><text></text></bio></artist></response>?

Part 2 (error) -
<?xml version="1.0"
encoding="utf-8" ?>
 <response status="error" version="1.2">
 <error code="9001">
 <errorMessage>Unhandled 7digital API server error.</errorMessage>
 </error>
</response>

We are not merging or threading any requests across our code.

Why do we receive a correct response followed directly by an error
code?

Aaron

We're confused with the behaviour you're experiencing, we can't duplicate
it with CURL, we don't see this behaviour with any other clients and you
say you can't duplicate it outside the application.

The API doesn't set a second response so would it be possible to have the
headers and any other information from the application?

http://blogs.7digital.com/dev/2011/07/29/improving-api-customer-support/

Regards

On 19 April 2012 15:41, Aaron Somal <aaronso...@googlemail.com> wrote:

Request Headers:
Request Method:GET
Status Code:200 OK
artistId:473615
oauth_consumer_key:OUR_KEY
country:GB

Response Headers:
Response        HTTP/1.1 200 OK
Server  nginx/0.7.67
Date    Thu, 19 Apr 2012 15:50:11 GMT
Content-Type    text/xml; charset=utf-8
Last-Modified   Tue, 17 Apr 2012 08:13:46 GMT
X-AspNet-Version        4.0.30319
x-7dig  aw1
Access-Control-Allow-Origin     *
Content-Length  502
Accept-Ranges   bytes
Cache-Control   private, max-age=432000
Age     200152
Expires Sun, 22 Apr 2012 08:14:19 GMT
x-cdn   Served by WebAcceleration
Connection      Keep-Alive

Does that help?

are you still experiencing problems?

If yes can you please contact us directly at a...@7digital.com ?

Thanks
Filip

On Apr 19, 5:00 pm, Aaron Somal <aaronso...@googlemail.com> wrote: