Skip to main content ↑ ↓

Notice

Please note that most of the software linked on this forum is likely to be safe to use. If you are unsure, feel free to ask in the relevant topics, or send a private message to an administrator or moderator. To help curb the problems of false positives, or in the event that you do find actual malware, you can contribute through the article linked here.
Topic: MP3 via HTTP—sometimes I get 404, but it works after some # of retries (Read 1372 times) previous topic - next topic
0 Members and 1 Guest are viewing this topic.

MP3 via HTTP—sometimes I get 404, but it works after some # of retries

Hello everyone.

I've noticed a strange thing while trying to open some mp3 files over http in foobar. When i try to listen to the entry, sometimes i get a 404 (not found) error, but after some errors(may be 10-20, or it might work from the first one) it starts playing. I don't think it has something to do with the server, because it is a major social network server(vk.com servers) and it works perfectly well when opening the same url in browser or other player. Also, from sniffing traffic, i found that every request sent by foobar is actually responded, like:
syn
syn+ack
ack
http get
http OK with data like
Quote
HTTP/1.1 200 OK
Server: nginx/1.2.1
Date: Sun, 10 Jun 2012 20:47:30 GMT
Content-Type: audio/mpeg
Content-Length: 3243523
Last-Modified: Sun, 09 Dec 2007 17:53:56 GMT
Connection: close
Expires: Wed, 27 Jun 2012 20:47:30 GMT
Cache-Control: max-age=1468800
Accept-Ranges: bytes

and then actual data stream.

So, i have no idea why foobar thinks it is 404. So far i found only some info about foobar ignoring wrong mime types over http, but it looks like they are ok, and it wouldn't allow for "sometimes" playing the track.
Also, i don't use any proxies or change http buffers etc.
I am using foo_vksearch to find tracks(links), but these links seem to be good, because they open up in browser.

So, this is the problem. Any advice would be appreciated. Sorry for possibly bad english in advance.

P.S. also i found out that browser opens http session like "keep-alive" while foobar gets data in pieces around 500kb using "closed" flag. But i don't know these http rules.