Bug 982736

Summary:	Cannot download podcast issue
Product:	Red Hat Enterprise Linux 7	Reporter:	Matěj Cepl <mcepl>
Component:	rhythmbox	Assignee:	Bastien Nocera <bnocera>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Desktop QE <desktop-qa-list>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	7.0	CC:	mcepl
Target Milestone:	rc
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
URL:	https://bugzilla.gnome.org/show_bug.cgi?id=703889
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2013-11-07 17:16:00 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Matěj Cepl 2013-07-09 17:33:54 UTC

Description of problem:
I have tried to use Rhythmbox for podcatching, but it apparently cannot download an issue.

Version-Release number of selected component (if applicable):
rhythmbox-2.99.1-1.el7.x86_64

How reproducible:
100%

Steps to Reproduce:
1.add http://feeds.americanpublicmedia.org/MarketplacePodcast?format=xml as a new podcast
2.update
3.try to download the latest one (the real URL of the issue is http://feeds.americanpublicmedia.org/~r/MarketplacePodcast/~5/6cjGo1_qbhI/marketplace_podcast_20130708_64.mp3)

Actual results:
Download "Failed"

Expected results:
issue downloaded

Additional info:
when I try to download with curl it works

curl -L -O http://feeds.americanpublicmedia.org/~r/MarketplacePodcast/~5/6cjGo1_qbhI/marketplace_podcast_20130708_64.mp3

Comment 2 Bastien Nocera 2013-11-07 13:59:13 UTC

There was a bug in the HTTP backend of gvfs that caused these problems. Is that fixed for you?

Comment 3 Matěj Cepl 2013-11-07 15:25:47 UTC

(In reply to Bastien Nocera from comment #2)
> There was a bug in the HTTP backend of gvfs that caused these problems. Is
> that fixed for you?

Way better. Thanks.

Comment 4 Bastien Nocera 2013-11-07 17:16:00 UTC

(In reply to Matěj Cepl from comment #3)
> (In reply to Bastien Nocera from comment #2)
> > There was a bug in the HTTP backend of gvfs that caused these problems. Is
> > that fixed for you?
> 
> Way better. Thanks.

I'll mark this as FIXED then.