|414 Request-URI Too Large||Marcus Almgren||7/20/11 11:18 AM|
If an end user is not already logged in, then after the authentication step the user is redirected to accounts.youtube.com/accounts/SetSID (along with a long sidt parameter in the querystring) and the result is an error page: "The requested URL /accounts/SetSID... is too large to process.". In this particular case I'm using 2-factor auth, but the point is that I can't change the request from a GET to a POST since I'm not the one doing the redirect to accounts.youtube.com -- it happens on the Google side.
The scope I'm requesting access to is Google Documents, but I guess Google is pushing my authentication to a bunch of sites in an SSO kind of way. I guess I could try deleting my Youtube account or disable 2-factor auth or whatever, but I'd really, really like to know why this is happening and how I can fix it.
|Re: 414 Request-URI Too Large||Marius Scurtescu||7/20/11 11:29 AM|
Would you be able to provide the full URL of the initial request?
|Re: 414 Request-URI Too Large||Marcus Almgren||7/20/11 11:52 AM|
The request chain starts with my web app redirecting the user to
upon which the end user is forwarded to
where the end user (me, in this case) enters username and password and unchecks the "Stay signed in" box. And since I've enabled 2-factor auth, I then get sent to
where I enter the OTP and don't check the "remember" checkbox and hit Confirm which redirects me to
Where it says
414. That’s an error. The requested URL /accounts/SetSID... is too large to process. That’s all we know.
By now, I'm already authenticated, so all I have to do is go back to my web app and I'm immediately sent to
and I can confirm and get sent back to my web app where everything works fine.
(The "someinteger", "subdomain.domain.com" etc. are obviously replacements for the actual values, but I can provide you with the actual values or the actual URL to the web app if that's of any assistance.)
|Re: 414 Request-URI Too Large||Marcus Almgren||7/27/11 1:36 AM|
Any word on this one? I'm doing a POC to see if our business should
move to Google Apps and this issue is kind of having a negative impact
on the demo factor ;)
> On Wed, Jul 20, 2011 at 2:18 PM, Marcus Almgren <marcusalmg...@gmail.com> wrote:> > I can fix it.- Hide quoted text -
> - Show quoted text -
|Re: 414 Request-URI Too Large||Marius Scurtescu||7/28/11 4:13 PM|
Thanks for reporting this problem and for providing all the details.
I am still investigating why did your request end up at YouTube, will
|Re: 414 Request-URI Too Large||Marcus Almgren||8/15/11 12:10 AM|
It's working as expected now, so I just wanted to say thanks for your prompt reaction. Very good.
|Re: 414 Request-URI Too Large||John Gilmore||1/3/12 3:35 PM|
We've been using oauth2.0 for a while and there were no problems.
Today we've experienced the same problems as described the Marcus - our request is definitely shorter then the one Marcus sent you
Is this a temporary problem ?
|Re: 414 Request-URI Too Large||Phil Chambers||3/13/12 5:06 AM|
We've recently implement oauth2 for Google at Podio and I'm seeing the same issue. I suspect it might be due to using accounts when multiple account signin is enabled. Can you confirm/deny if you have a known issue and if not I'll give a more complete bug report?
|Re: 414 Request-URI Too Large||Marius Scurtescu||3/13/12 4:16 PM|
There was an issue last summer, and it was related to accounts that
had strong auth enabled. It was fixed at the time.
Are these accounts strong auth enabled? Does the user get a chance to
|Re: 414 Request-URI Too Large||Unfolding Apps Inc.||4/27/12 2:03 PM|
Sorry for the delay and many thanks