Auto-tag from web...: HTTP/1.1 400 Bad Request [BUG# 5605]
Moderator: Gurus
-
jackderrippa
Re: Auto-tag - Couldn't show results: HTTP/1.1 400 Bad Request
For what it's worth, it's happening to me too. Just started, and *highly* annoying.
Re: Auto-tag - Couldn't show results: HTTP/1.1 400 Bad Request
I am glad I finally opted to check the MM forum as I bought a new CD today and it would not load the track or find it - getting the Bad Request error, too. I can say all was well last night for me and noticed this problem around 2 PM PST. I suspected something may be amiss with the Amazon link since Windows MP uses a different source and is working fine. I hope this is resolved quickly as it annoying but glad to see it is not an issue with MM.
-
alchemy420
Re: Auto-tag - Couldn't show results: HTTP/1.1 400 Bad Request
yeah, japan was the only one working for me earlier but now it's not working either!!!!Guest wrote:It must have started a few hours ago as it was working this morning around 11am. Probably an Amazon glitch. Not sure. It looks as if the Amazon.co.jp works, but the others dont.
You may see if you can find the album on the jp option, and it could pop up US import (if you are in the US) and go that route until it glitch is fixed somewhere.
-
Guest
Re: Auto-tag - Couldn't show results: HTTP/1.1 400 Bad Request
Well, looks like we know we have a problem, and since everyone is experiencing it, we wait. No need to keep posting "it doesn't work for me either" The MM team is aware and working on it for us. I'm sure by morning when I wake up, it will be just fine 
-
guest
Re: Auto-tag - Couldn't show results: HTTP/1.1 400 Bad Request
Why not use Google images to get the album cover art. I have been using that when the album art present by media monkey was not at least 300x300. And now that the cover art downloader is not working, that is where I am manually downloading it now.
-
samitgaur
Re: Auto-tag - Couldn't show results: HTTP/1.1 400 Bad Request
Same here .. for me only Amazon.ca works but that too says "No results found" for seemingly hit songs. 
-
thecongressman
- Posts: 28
- Joined: Sun Mar 30, 2008 3:38 pm
Re: Auto-tag - Couldn't show results: HTTP/1.1 400 Bad Request
aaaaaaaaaaaaaaaaaaaaaaaaaaaahhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhh
my life has now screeched to a halt! now i must go do something productive while the mm guys get on it. like drink a beer.
my life has now screeched to a halt! now i must go do something productive while the mm guys get on it. like drink a beer.
Over 280,000 songs and Mediamonkey is still going strong...
-
cabravo31
Re: Auto-tag - Couldn't show results: HTTP/1.1 400 Bad Request
Yeah, Same here. MM, please fix this!!!
-
Atomiclizard
Re: Auto-tag - Couldn't show results: HTTP/1.1 400 Bad Request
MediaMonkey, I've loved you since the day we met...DON'T LET ME DOWN!!
-
ElectroLuxx
- Posts: 7
- Joined: Mon Jun 05, 2006 5:44 pm
- Location: USA
Re: Auto-tag - Couldn't show results: HTTP/1.1 400 Bad Request
UPDATE: I posted on this earlier (2nd poster, I believe.)
Any app using an embedded IE control (MediaMonkey, Rhapsody, etc.) or IE 8 itself can't connect to the internet. I hadn't noticed it before today. I normally use FireFox as my browser, so the IE 8 issue wasn't immediately apparent.
Don't know if that helps you developers, but it's all I have at the moment.
Any app using an embedded IE control (MediaMonkey, Rhapsody, etc.) or IE 8 itself can't connect to the internet. I hadn't noticed it before today. I normally use FireFox as my browser, so the IE 8 issue wasn't immediately apparent.
Don't know if that helps you developers, but it's all I have at the moment.
-
nohitter151
- Posts: 23640
- Joined: Wed Aug 09, 2006 10:20 am
- Location: NJ, USA
- Contact:
Re: Auto-tag - Couldn't show results: HTTP/1.1 400 Bad Request
Other auto-tag scripts don't seem to be affected:
http://www.mediamonkey.com/forum/viewto ... oo#p195396
http://www.mediamonkey.com/forum/viewto ... oo#p195396
MediaMonkey user since 2006
Need help? Got a suggestion? Can't find something?
Please no PMs in reply to a post. Just reply in the thread.
Need help? Got a suggestion? Can't find something?
Please no PMs in reply to a post. Just reply in the thread.
Re: Auto-tag - Couldn't show results: HTTP/1.1 400 Bad Request
That's it, it's all over!!! I think I'll follow the advice of getting a beer or 20...
Can't access any Amazon site, nor Japan nor Ca....
Also, my MM has gotten really slow! Takes forever to re-catalogue my library when it opens up and just hangs to the point I figure it has frozen. Maybe a background attempt to connect to the internet?
-
ElectroLuxx
- Posts: 7
- Joined: Mon Jun 05, 2006 5:44 pm
- Location: USA
Re: Auto-tag - Couldn't show results: HTTP/1.1 400 Bad Request
Update to my Update ---
I was able to restore IE 8 connectivity, but MediaMonkey still can't connect to Amazon for lookups. Other apps using an IE control (Rhapsody, etc.) seem to work as well.
Sorry if my last post confused things.
I was able to restore IE 8 connectivity, but MediaMonkey still can't connect to Amazon for lookups. Other apps using an IE control (Rhapsody, etc.) seem to work as well.
Sorry if my last post confused things.
-
bigbadger
Re: Auto-tag - Couldn't show results: HTTP/1.1 400 Bad Request
Still not working - glad I looked here - eventually - many hours wasted - been thinking its something on my PC - pity MM don't have a information page with any known current issues.
-
frustrated_MM_User
Re: Auto-tag - Couldn't show results: HTTP/1.1 400 Bad Request
Same here,
actually quite happy that i'm not the only one affected.
cant wait for it to get fixed
actually quite happy that i'm not the only one affected.
cant wait for it to get fixed