Auto-tag from web...: HTTP/1.1 400 Bad Request [BUG# 5605]
Moderator: Gurus
-
Guest
Re: Auto-tag - Couldn't show results: HTTP/1.1 400 Bad Request
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.
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
I like Budweiser Budvar, the REAL budweiser. And Pilsner Urquell!
(yeah I got the same thing).
(yeah I got the same thing).
Last.fm: http://www.last.fm/user/pathduck
Re: Auto-tag - Couldn't show results: HTTP/1.1 400 Bad Request
Posting so I am notified if fix. Love this feature...
Re: Auto-tag - Couldn't show results: HTTP/1.1 400 Bad Request
The problem is fixed, will be ok in the next release.
-
Polarisky
Re: Auto-tag - Couldn't show results: HTTP/1.1 400 Bad Request
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. 
-
usandstuff
- Posts: 3
- Joined: Tue Aug 18, 2009 3:18 pm
Re: Auto-tag - Couldn't show results: HTTP/1.1 400 Bad Request
yeah, I'd like to see more than amazon, Gracenote would be a nice addition
-
APR
Re: Auto-tag - Couldn't show results: HTTP/1.1 400 Bad Request
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
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.
"I wish you well!" - Rex Stout
Re: Auto-tag - Couldn't show results: HTTP/1.1 400 Bad Request
@Karolm
The solution will need to come from Amazon or MediaMonkey. Us users can't resolve this issue.
The solution will need to come from Amazon or MediaMonkey. Us users can't resolve this issue.
Download MediaMonkey ♪ License ♪ Knowledge Base ♪ MediaMonkey for Windows 2024 Help ♪ MediaMonkey for Android Help
Lowlander (MediaMonkey user since 2003)
Lowlander (MediaMonkey user since 2003)
Re: Auto-tag - Couldn't show results: HTTP/1.1 400 Bad Request
No need to submit support tickets as this is issue is known and being worked on.nynaevelan wrote: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??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
Download MediaMonkey ♪ License ♪ Knowledge Base ♪ MediaMonkey for Windows 2024 Help ♪ MediaMonkey for Android Help
Lowlander (MediaMonkey user since 2003)
Lowlander (MediaMonkey user since 2003)
Re: Auto-tag - Couldn't show results: HTTP/1.1 400 Bad Request
Re MiPi posting: do you mean we have to wait till the next release of MM?
"I wish you well!" - Rex Stout
-
Guest
Re: Auto-tag - Couldn't show results: HTTP/1.1 400 Bad Request
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
http://www.ventismedia.com/mantis/view.php?id=5605
Re: Auto-tag - Couldn't show results: HTTP/1.1 400 Bad Request
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?
"I wish you well!" - Rex Stout
-
thecongressman
- Posts: 28
- Joined: Sun Mar 30, 2008 3:38 pm
Re: Auto-tag - Couldn't show results: HTTP/1.1 400 Bad Request
So does anyone have any idea when the new build will be released?
Over 280,000 songs and Mediamonkey is still going strong...