New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Find a proper way of supporting resumable uploads #131

Open
michielbdejong opened this Issue Nov 30, 2015 · 5 comments

Comments

4 participants
@michielbdejong
Copy link
Member

michielbdejong commented Nov 30, 2015

We had to remove Content-Range headers on PUT requests in #118 - so we will need to find a better solution for resumable uploads.

@fkooman

This comment has been minimized.

@untitaker

This comment has been minimized.

Copy link
Member

untitaker commented Dec 3, 2015

The Google Way is what we removed, I think it can/should be ruled out.

The other libraries don't seem to talk about the underlying HTTP semantics at all.

@michielbdejong

This comment has been minimized.

Copy link
Member

michielbdejong commented Dec 10, 2015

@untitaker the reason you don't like the way Google Drive does it is that it seems to violate the HTTP RFC to use Content-Range on PUT, right? Do you have a better idea? We could make it X-Content-Range :)

@untitaker

This comment has been minimized.

Copy link
Member

untitaker commented Dec 10, 2015

Yes, just because it violates the RFC. I think it's tragic that this was explicitly disallowed, the way Google does it was very elegant until the new HTTP RFCs came along. Perhaps somebody from the IETF has a better suggestion?

@skddc

This comment has been minimized.

Copy link
Member

skddc commented Feb 3, 2018

@untitaker and I just had a nice long IRL discussion about what's missing for a 1.0 final of the RS spec. We agree that this is probably the most important missing feature at the moment.

Using an X-Content-Range header would work I think. If we apply for RFC status, this topic would also be reviewed by the IESG then. Or we can ask on an IETF mailing list beforehand.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment