I've recently been getting an error when loading an album from Discogs - "Bad HTTP Status Code". I am on version 6.4.9. This has started recently (Like today only). Any idea what may be causing this error?
Printable View
I've recently been getting an error when loading an album from Discogs - "Bad HTTP Status Code". I am on version 6.4.9. This has started recently (Like today only). Any idea what may be causing this error?
The change in Discogs API on February 1st caused it.Quote:
Originally Posted by j_castellano@comcast.net
But it is fixed now. You can grab new build from website.
Andrei
I started getting this error message again on 12-19-2014. Has there been another change in Discogs API? Is a fix in the works?
Thanks
Yes, and unfortunately it's a bigger change that is harder to fix than before.Quote:
Originally Posted by gjetson
The new build is coming in early January.
Sorry about the wait.
Andrei
Hi Andrei
January has come and gone... ;O) any new on an update?
While we are at it.. any new on your shiny new replacement [ if any ] to OCD?
Andrei,
It was working briefly in January, but now trying to add an album from Discogs returns the "Bad HTTP Code Status." Any hope for a fix soon? I've got lots of new vinyl I want to add to my collection.
Thanks
Hi!
The problem is not only with Discogs. I am getting the same thing with Freedb. Since Discogs wasn't working Ithought I would use Freedb and just change some of the information... but that isn't possible.
Discogs doesn't even access their database to load results based on your search input.
Here is a Discogs log (search term "artist" beatles):
Connecting to api.discogs.com
>| GET /database/search?artist=beatles&oauth_consumer_key=DZqYcaUCZ BreeEHlYxXY&oauth_nonce=rI8UR1JFEI4_UWXiAir&oauth_ signature_method=HMAC-SHA1&oauth_timestamp=1424867400&oauth_token=NyCQcf amXCTuNMSNXSeIixKOYwMkBYsNrxQMjIST&oauth_version=1 .0&page=1&per_page=100&type=release&oauth_signatur e=B%2B4Y7mXaSPkmgnBLwauP%2FSIDxVQ%3D HTTP/1.1
>| Accept-Encoding: gzip
>| User-Agent: OrangeCD 6.5
>| Host: api.discogs.com
>| Connection: Keep-Alive
>|
<| HTTP/1.1 401 Unauthorized
<| Reproxy-Status: yes
<| Access-Control-Allow-Origin: *
<| Cache-Control: public, must-revalidate
<| Content-Type: application/json
<| WWW-Authenticate: OAuth realm="http://api.discogs.com"
<| Content-Length: 61
<| Connection: close
<| Date: Wed, 25 Feb 2015 12:30:03 GMT
<| Server: lighttpd
<|
<| {"message": "You must authenticate to access this resource."}
I am authenticated at Discogs and have been for awhile.
Once again, using the search "artists" beatles, freedb goes one step further than Discogs and brings up a number of albums, but when you click on one of the albums for extra information you get the bad HTTP status message. See log below:
Connecting to freedb.mygenres.com
>| GET /freedb/blues/b207260d HTTP/1.1
>| User-Agent: OrangeCD 6.5
>| Host: freedb.mygenres.com
>| Connection: Keep-Alive
>|
<| HTTP/1.1 404 Not Found
<| Date: Wed, 25 Feb 2015 12:25:57 GMT
<| Server: Apache/2.2.3 (CentOS)
<| Content-Length: 303
<| Connection: close
<| Content-Type: text/html; charset=iso-8859-1
<|
<| <!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">
<| <html><head>
<| <title>404 Not Found</title>
<| </head><body>
<| <h1>Not Found</h1>
<| <p>The requested URL /freedb/blues/b207260d was not found on this server.</p>
<| <hr>
<| <address>Apache/2.2.3 (CentOS) Server at freedb.mygenres.com Port 80</address>
<| </body></html>
Thanks for looking into this Andrei! It is really really appreciated.
I resorted to adding the information via Amazon. Guess what suddenly happened after I successfully added 2 albums?
See the log below:
Connecting to ecs.amazonaws.fr
>| GET /onca/xml?AWSAccessKeyId=0KVBS3ZNNEXJ2JXM9C02&Artist=Myl %E8ne%20Farmer&AssociateTag=orangesuitemu-20&ItemPage=1&Operation=ItemSearch&ResponseGroup=I temAttributes%2CImages&SearchIndex=Music&Service=A WSECommerceService&Timestamp=2015-02-25T13%3A32%3A32Z&Version=2011-08-01&Signature=X58gLublNxE2iOnCmlbjL%2B4nI5phi3rVbge 2uHHgPGg%3D HTTP/1.1
>| User-Agent: OrangeCD 6.5
>| Host: ecs.amazonaws.fr
>| Connection: Keep-Alive
>|
<| HTTP/1.1 403 Forbidden
<| Date: Wed, 25 Feb 2015 13:32:34 GMT
<| Server: Apache-Coyote/1.1
<| Vary: Accept-Encoding,User-Agent
<| nnCoection: close
<| Content-Length: 427
<|
<| (binary data)
<|
Thank you Andrei! It looks like build 6.5.5.20914 solves the problem.
I get this, too - ver. 6.5.5
Is a fix coming?
Connecting to freedb.mygenres.com
>| GET /freedb/jazz/6e0f0808 HTTP/1.1
>| User-Agent: OrangeCD 6.5
>| Host: freedb.mygenres.com
>| Connection: Keep-Alive
>|
<| HTTP/1.1 404 Not Found
<| Date: Thu, 04 Jun 2015 01:44:16 GMT
<| Server: Apache/2.2.3 (CentOS)
<| Content-Length: 302
<| Connection: close
<| Content-Type: text/html; charset=iso-8859-1
<|
<| <!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">
<| <html><head>
<| <title>404 Not Found</title>
<| </head><body>
<| <h1>Not Found</h1>
<| <p>The requested URL /freedb/jazz/6e0f0808 was not found on this server.</p>
<| <hr>
<| <address>Apache/2.2.3 (CentOS) Server at freedb.mygenres.com Port 80</address>
<| </body></html>