Hello All,
Just to close the loop here, a fix for this behavior has been
written, and the authentication token will only need to be valid at
the time the metadata is initially submitted for the upload to
succeed.
The timeline for rolling it out to production should be about two
weeks. Thanks for everyone's patience while this was being worked on
internally.
Cheers,
-Jeff Posnick, YouTube API Team
groups.google.com/group/youtube-api-gdata | apiblog.youtube.com |
@YouTubeDev
On Apr 10, 8:20 am, Jeffrey Posnick <je...@google.com> wrote:
> Hello Soren,
>
> My gut feeling would be weeks rather than months, but I should know
> more after I chase some people down internally this week.
>
> I agree that it would be ideal to reject the metadata at the start
> rather than end of a resumable upload, and I'll ask about that as
> well.
>
> Cheers,
> -Jeff Posnick, YouTube API Team
> groups.google.com/group/youtube-api-gdata | apiblog.youtube.com |
> @YouTubeDev
>
> On Apr 5, 3:56 am, Soren Dreijer <dreijer...@gmail.com> wrote:
>
>
>
>
>
>
>
> > Do you have any idea whether we're talking weeks or months here? YouTube
> > has huge file size caps for uploaded videos, but your API requires it to
> > happen within less than an hour. That sounds to me like a major bug
> > preventing a lot of applications from interacting with YouTube. We have a
> > lot of users onwww.evolvehq.comwho'dlove to upload their videos but are
> > currently unable to unless they're on a blazingly fast Internet connection.
>
> > Speaking of server-side fixes, are you guys planning on returning error
> > responses before a full video has been uploaded? For instance, I can pass
> > invalid XML in the initial POST to create the resumable upload, but I won't
> > get an error back until the full video has been uploaded. That's a waste of
> > bandwidth for both YouTube and the user who's trying to upload the video.
>
> > Cheers,
> > Soren
>
> > On Wednesday, April 4, 2012 12:35:34 PM UTC-7, Jeffrey Posnick wrote:
>
> > > Hello Soren,
>
> > > It's going to be addressed server-side, but I'm afraid that short of
> > > switching to AuthSub (which doesn't have any expiration) there's no
> > > recommended workaround at this time.
>
> > > I will update this thread when the issue is addressed.
>
> > > Cheers,
> > > -Jeff Posnick, YouTube API Team
> > > groups.google.com/group/youtube-api-gdata | apiblog.youtube.com |
> > > @YouTubeDev
>
> > > On Apr 2, 5:22 pm, Soren Dreijer <dreijer...@gmail.com> wrote:
> > > > Hi Jeff,
>
> > > > So, does this essentially mean that users who are unable to upload
> > > videos
> > > > within an hour will never be able to successfully upload their videos to
> > > > YouTube? That sounds like a major issue to me...
>
> > > > Our users are uploading quite large videos due to the way they're
> > > generated
> > > > and I imagine quite a few of them won't be able to upload the videos
> > > within
> > > > an hour on an ordinary broadband connection.
>
> > > > Is there anything we can do to work around this or somehow get YouTube
> > > to
> > > > acknowledge this as a major bug?
>
> > > > Cheers,
> > > > Soren
>
> > > > On Monday, April 2, 2012 1:49:26 PM UTC-7, Jeffrey Posnick wrote:
>
> > > > > Hello Soren,
>
> > > > > Yes, my understanding of the current behavior is that the
> > > > > Authentication token that was used in the initial metadata submission
> > > > > needs to be valid at the time the upload completes, and that this is
> > > > > leading to the 401s that you and a few other developers have been
> > > > > reporting. Continuing an upload and completing it two hours later
> > > > > would presumably trigger the problem.
>
> > > > > I don't have anything additional to pass along from the engineering
> > > > > team yet, but assuming that assessment of the bug is correct, it's
> > > > > definitely something that needs to be fixed on our end via a server-
> > > > > side code change.
>
> > > > > Cheers,
> > > > > -Jeff Posnick, YouTube API Team
> > > > > groups.google.com/group/youtube-api-gdata | apiblog.youtube.com |
> > > > > @YouTubeDev
>
> > > > > On Mar 29, 12:42 pm, Soren Dreijer <dreijer...@gmail.com> wrote:
> > > > > > Hi Jeff,
>
> > > > > > Thanks for getting back to me. So first of all, I found a mistake in
> > > my
> > > > > own
> > > > > > code that didn't properly refresh the access token I used when
> > > uploading
> > > > > > the video, which caused any videos I was uploading after a while
> > > > > (resumable
> > > > > > or not) to fail with a 401. The reason I didn't notice the issue is
> > > > > because
> > > > > > YouTube doesn't give me a 401 when I initially start the upload,
> > > i.e.
> > > > > when
> > > > > > I send the POST request that contains all the Authorization headers.
> > > > > > Instead, YouTube lets me think everything is fine and dandy (I even
> > > get
> > > > > my
> > > > > > resumable URL back with an upload token in it) and it lets me upload
> > > the
> > > > > > entire video before it finally spits a 401 at me. That should
> > > probably
> > > > > be
> > > > > > changed.
>
> > > > > > Also, what happens if I start an upload with an access token, the
> > > upload
> > > > > is
> > > > > > interrupted and I then try to resume it two hours laters? Will I
> > > then
> > > > > get a
> > > > > > 401?
>
> > > > > > Cheers,
> > > > > > Soren
>
> > > > > > On Tuesday, March 27, 2012 10:14:17 AM UTC-7, Jeffrey Posnick wrote:
>
> > > > > > > Hello Soren,
>
> > > > > > > An OAuth 2 access token expires after an hour, at which point a
> > > new
> > > > > > > access token needs to be obtained in exchange for a refresh token.
> > > > > > > (The refresh token never expires.) I do recall a bug that sounds
> > > like
> > > > > > > what you're experiencing where the access token is checked after
> > > the
> > > > > > > upload is complete rather than when the upload begin, meaning that
> > > if
> > > > > > > the upload takes some time to complete there's a chance the token
> > > will
> > > > > > > have expired once it's done.
>
> > > > > > > I'll try to track down that bug internally and see if we can get
> > > a
> > > > > > > resolution prioritized, since we definitely don't want to prevent
> > > > > > > people from using OAuth 2 and resumable uploads.
>
> > > > > > > Cheers,
> > > > > > > -Jeff Posnick, YouTube API Team
> > > > > > > groups.google.com/group/youtube-api-gdata | apiblog.youtube.com |
> > > > > > > @YouTubeDev
>
> > > > > > > On Mar 24, 11:55 pm, Soren Dreijer <dreijer...@gmail.com> wrote:
> > > > > > > > Hi there,
>
> > > > > > > > I'm attempting to use the resumable API to upload a video to
> > > YouTube
> > > > > (as
> > > > > > > > documented here:
>
> > >https://developers.google.com/youtube/2.0/developers_guide_protocol_r...),
>
> > > > > > > > but I'm getting a 401 back when I've finished uploading the
> > > resumed
> > > > > part
> > > > > > > of
> > > > > > > > the data. I get the following message back alongside the 401:
>
> > > > > > > > *Token invalid - Invalid token: Stateless token expired*
>
> > > > > > > > I'm able to start the resume operation just fine (i.e. I get a
> > > 308
> > > > > back
> > > > > > > and
> > > > > > > > no updated Location field), but when I've finished uploading the
> > > > > rest of
> > > > > > > > the video, the above response comes back.
>
> > > > > > > > Any ideas?
--
You received this message because you are subscribed to the Google Groups "YouTube APIs Developer Forum" group.
To post to this group, send email to youtube-api-gdata@googlegroups.com.
To unsubscribe from this group, send email to youtube-api-gdata+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/youtube-api-gdata?hl=en.
No comments:
Post a Comment