I think that the problem is actually that listening.at refuses to respond
helpfully to an HTTP HEAD request on port 8000: it instead returns a 400 Bad
Request error.
RFC 2616, Hypertext Transfer Protocol -- HTTP/1.1, states:
The metainformation contained in the HTTP headers in response to a HEAD
request SHOULD be identical to the information sent in response to a GET
request.
http://tools.ietf.org/html/rfc2616#section-9.4
Rhythmbox’s debug output includes:
rb-podcast-manager.c:699: get_file_info request failed
Presumably, it is making an HTTP HEAD request to find information on the file
that is to be downloaded.
You can verify how http://listening.at:8000 responds to an HTTP HEAD request
by, for example, running:
curl --head http://listening.at:8000/ueberklang/ueber220608.mp3
In case you do not have curl, I’ll mention that wget’s spider option seems to
work by making HEAD requests; in any case, in this instance it responds in the
same way:
wget --spider --server-response
http://listening.at:8000/ueberklang/ueber220608.mp3
It looks to me that this is not a bug in Rhythmbox, but rather a bug, or at
least undesirable behaviour, in listening.at, so I am marking this bug as
Invalid. Of course, you may wish to contact Überklang to inform them of this
problem.
** Changed in: rhythmbox (Ubuntu)
Status: New => Invalid
--
Rhythmbox cannot download some podcasts (port 8000)
https://bugs.launchpad.net/bugs/247123
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to rhythmbox in ubuntu.
--
desktop-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
