Bug 1882028 - Handle 308 redirect change of behavior
Summary: Handle 308 redirect change of behavior
Keywords:
Status: CLOSED DUPLICATE of bug 2015282
Alias: None
Product: Fedora
Classification: Fedora
Component: PyDrive
Version: 34
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Nick Bebout
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-09-23 16:00 UTC by Michael Terry
Modified: 2021-10-25 16:03 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-10-25 16:03:57 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Michael Terry 2020-09-23 16:00:01 UTC
Description of problem:
httplib2 0.16 changed how 308 redirects are handled. This broke some existing python packages that weren't expecting that change when talking to Google servers that use 308 redirects. Like PyDrive.

Version-Release number of selected component (if applicable):
1.3.1

How reproducible:
A little difficult. I'm not entirely sure how, but it involves uploading a large or a lot of files and then eventually this error shows up.

I'm seeing this manifest higher up the chain with bug reports of errors like "RedirectMissingLocation: Redirected but the response is missing a Location: header"

Additional info:
Some history in these issues:
https://github.com/httplib2/httplib2/issues/156
https://github.com/googleapis/google-api-python-client/issues/803
https://gitlab.gnome.org/World/deja-dup/-/issues/74

The pydrive2 project landed these patches to fix it:
https://github.com/iterative/PyDrive2/compare/c2609b74f41569f81e98376ab6cbc71333e82848...18537bbb5b9a7eee38c84bc1bbea46faf42c18b4

Maybe we could just apply those patches to this package too.

Comment 1 Ben Cotton 2021-02-09 15:19:04 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 34 development cycle.
Changing version to 34.

Comment 3 Matthew Miller 2021-10-21 14:54:18 UTC
It looks like what we need to do is replace (dead project) PyDrive with (maintained fork) PyDrive2 (https://pypi.org/project/PyDrive2/)?

Comment 4 Michael Terry 2021-10-21 15:14:10 UTC
That is a reasonable thing to do, sure.

It’s designed as a drop-in replacement. It has a different import path, but at least some consumers try to import both.

Comment 5 Matthew Miller 2021-10-21 15:32:14 UTC
I see that Marty has beaten me to that idea -- what do you think about closing this bug as a duplicate of #2015282?

Comment 6 Michael Terry 2021-10-21 17:23:39 UTC
With my reporter hat on, that’s totally fine and would solve the issue for me.

Duplicity looks for both old and new pydrive, so it can handle the change transparently.

Comment 7 Matthew Miller 2021-10-25 16:03:57 UTC

*** This bug has been marked as a duplicate of bug 2015282 ***


Note You need to log in before you can comment on or make changes to this bug.