** Changed in: rhythmbox
Status: Unknown => Invalid
** Changed in: rhythmbox
Importance: Unknown => Medium
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/247123
Title:
Rhythmbox cannot dow
** Bug watch added: GNOME Bug Tracker #728639
https://bugzilla.gnome.org/show_bug.cgi?id=728639
** Also affects: rhythmbox via
https://bugzilla.gnome.org/show_bug.cgi?id=728639
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member of U
Looking at the debug log from both rhythmbox and my test code, I can
confirm this. Note that if I change the server and podcast XML to port
80 this test works fine.
When I add the podcast URL, rbox debug output clearly references 8080
(10:06:42) [0x2655ca0] [rb_uri_could_be_podcast] rb-file-help
I've confirmed this two ways
1) I used a python program to mock a web server, I've checked it responds to
HEAD requests on non-standard ports
2) When I right click on a podcast feed and select properties, I can see that
it is not showing the port number on the URL, even though I know it does in
For completeness, here is a log to show that Rhythmbox does indeed make a HEAD
request:
HEAD /ueberklang/ueber220608.mp3 HTTP/1.1
Host: listening.at:8000
User-Agent: gnome-vfs/2.22.0 neon/0.25.4
Keep-Alive:
Connection: TE, Keep-Alive
TE: trailers
HTTP/1.0 400 Bad
So I wrote a mail to tech at ueberklang.net, even though I don't have
much hope that anything changes that way.
So I actually installed Icecast2 and I could easily reproduce the bug. I
filed Bug 248386 in launchpad, and I hope someone forwards it to their
upstream bug tracker.
Icecast seems to be
It seems that Überklang is running Icecast2, so you could install
apt:icecast2, try to reproduce the bug in that, and file a bug here in
Launchpad or upstream if you manage to do so. There are mailing list posts
from November 2006 regarding Icecast’s lack of support for HTTP HEAD, so I
don’t k
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
