Hi, 

I'm getting the above error for our DA app:

http://profile.myspace.com/index.cfm?fuseaction=user.viewprofile&friendid=412251422

I've read the recent blog post about this error, and I've set the external domain to

http://www.coolchaser.com

and external url to:

http://www.coolchaser.com/myspace/user_info

To access the DA app, go to 

http://www.coolchaser.com/myspace/pre

What am I doing wrongly?

Thanks,

chao

 

 Blogs:

 

http://developer.myspace.com/Community/blogs/devteam/archive/2008/09/22/fixing-oauth-404-errors-with-data-availability.aspx

 Hi Rhonda, yes I have read that blog post as I mentioned in the post above. I think I've followed all the directions but am still getting the error. Help!

 

Thanks,

chao

I'm also still seeing this problem despite having followed the instructions in that blog post - see my reply (comment #2).

Grateful for any help or pointers.

-- Richard

 This is still hapenning. I think it has to do with what we've seen before, where only developers of the application can use it.

What we've noticed is that for a user that is a developer of the application, the auth process succeeds. For a user who is not a developer, we get the 404 error.

Please check it.

 Ok, checking in :)

Hi everyone,

Sorry for the inconvenient. There is a bug in the validation process and it has been fixed but has not rolled to production yet.
There is a solution around it until the fix rolls out.


Please try the following changes to External Domain to get it working.
Remove the subdomain or domain prefix from the "External Domain:" (this is found under External Site Settings).
Remove the path and querystring from the url.
Ex.
http://www.myspace.com/mdp?a=1&b=2
becomes
http://myspace.com



Just so everyone is aware. The future/new validation will work as follow:
The protocol/scheme (http://, ftp://, aim://, your custom protocol, etc) will be checked in addition to the domain.tld (myspace.com, if www.myspace.com it will just check for myspace.com). This helps with desktop applications that want to use the callback. These two values are compared against the oauth_callback.

Hope this helps
-V

 Thank you, looks like this workaround is working.