Page 4 of 13
Re: Auto-tag - Couldn't show results: HTTP/1.1 400 Bad Request
Posted: Tue Aug 18, 2009 2:38 pm
by Guest
Every search will give this error -- Amazon added an extra encryption/authentication step to its programming API. Here's another web site that was affected:
http://blog.bookmooch.com/2009/08/18/am ... ay-or-two/
Hopefully MediaMonkey can get an update out ASAP to fix it.
Re: Auto-tag - Couldn't show results: HTTP/1.1 400 Bad Request
Posted: Tue Aug 18, 2009 2:41 pm
by ASAP
Re: Auto-tag - Couldn't show results: HTTP/1.1 400 Bad Request
Posted: Tue Aug 18, 2009 2:46 pm
by Pathduck
I like Budweiser Budvar, the REAL budweiser. And Pilsner Urquell!
(yeah I got the same thing).
Re: Auto-tag - Couldn't show results: HTTP/1.1 400 Bad Request
Posted: Tue Aug 18, 2009 2:51 pm
by docbells
Posting so I am notified if fix. Love this feature...
Re: Auto-tag - Couldn't show results: HTTP/1.1 400 Bad Request
Posted: Tue Aug 18, 2009 3:03 pm
by MiPi
The problem is fixed, will be ok in the next release.
Re: Auto-tag - Couldn't show results: HTTP/1.1 400 Bad Request
Posted: Tue Aug 18, 2009 3:09 pm
by Polarisky
What I'd like to see added to MM is to have a choice of which CD DB we want to use, there is more than Amazon out there available, and one of my other apps gives the choice of FreeDB which is just fine.
Re: Auto-tag - Couldn't show results: HTTP/1.1 400 Bad Request
Posted: Tue Aug 18, 2009 3:19 pm
by usandstuff
yeah, I'd like to see more than amazon, Gracenote would be a nice addition
Re: Auto-tag - Couldn't show results: HTTP/1.1 400 Bad Request
Posted: Tue Aug 18, 2009 3:38 pm
by APR
Worked for me just a few minutes again, just once, then the same problem....
Re: Auto-tag - Couldn't show results: HTTP/1.1 400 Bad Request
Posted: Tue Aug 18, 2009 3:41 pm
by Karolm
I tried adding Amazon.com to my trusted sites list (required dropping the requirement of the secure server, since they are http, not https). That did not help, so don't bother.
Re: Auto-tag - Couldn't show results: HTTP/1.1 400 Bad Request
Posted: Tue Aug 18, 2009 3:44 pm
by Lowlander
@Karolm
The solution will need to come from Amazon or MediaMonkey. Us users can't resolve this issue.
Re: Auto-tag - Couldn't show results: HTTP/1.1 400 Bad Request
Posted: Tue Aug 18, 2009 4:19 pm
by Lowlander
nynaevelan wrote:domidomi wrote:the dudes are not working on the problem! in their bugtracker is no post within the last 2 months.
deam - i loved this feature
Just because a ticket is not showing in Mantis does not mean the problem is not being addressed. Have any of you put in a support ticket for assistance to this??
No need to submit support tickets as this is issue is known and being worked on.
Re: Auto-tag - Couldn't show results: HTTP/1.1 400 Bad Request
Posted: Tue Aug 18, 2009 5:15 pm
by Karolm
Re MiPi posting: do you mean we have to wait till the next release of MM?
Re: Auto-tag - Couldn't show results: HTTP/1.1 400 Bad Request
Posted: Tue Aug 18, 2009 5:25 pm
by Guest
The issue is resolved but the new build (MM 3.1.1.1257) has not been released yet:
http://www.ventismedia.com/mantis/view.php?id=5605
Re: Auto-tag - Couldn't show results: HTTP/1.1 400 Bad Request
Posted: Tue Aug 18, 2009 6:37 pm
by Karolm
Re last post by "Guest": I take it to mean "yes" (unfortunately) to my question. Also, re posting in this topic by Polarisky: I couldn't agree more! After all, freedb and others like it probably do not create any access problems, right?
Re: Auto-tag - Couldn't show results: HTTP/1.1 400 Bad Request
Posted: Tue Aug 18, 2009 7:55 pm
by thecongressman
So does anyone have any idea when the new build will be released?
