403 Forbidden: The server understood the request, but is refusing to fulfill it


#1

I finally figured out how to reproduce this:

  1. Log into Twitter with my user account. Make sure I check Remember me.
  2. Run a sample app to perform a normal Web OAuth authentication.
  3. Normally, the authentication screen indicates that I am logged in and I would only see the Authorize button. However, in this case I see an authorization screen that asks for Username and Password with no indication that I’m already logged in.
  4. I fill in Username and Password and click Authorize App.
  5. I receive “403 Forbidden: The server understood the request, but is refusing to fulfill it.” in response to POST https://api.twitter.com/oauth/authorize HTTP/1.1.

If I log out of my Twitter account, I can authorize with no problem. Also, If I’m logged in, but haven’t clicked Remember me, then everything works fine.

Also, this works for ASP.NET MVC, but not ASP.NET Web Forms. They both use the same exact code to build the OAuth signature. Tracing the HTTP traffic, the only difference in the signatures I send to you is that ASP.NET Web Forms (the example with the problem) has a callback url that ends with “.aspx”. The other example contains a friendly URL that doesn’t indicate a file with a suffix and it works fine. The cookies (keys) also appear to be different between request types.

Joe


#3

While creating a widget I get the infamous 403 Forbidden: The server understood the request, but is refusing to fulfill it. Please let me know what can I do to create a widget.
Thanks!
Adriana.


#4

Having the same issue when attempting to create a widget:

“403 Forbidden: The server understood the request, but is refusing to fulfill it.”

Please help!


#5

same here!


#6

Same thing. Can we have an answer please ?


#7

Omg ,Same issue Here . Still wait for Answer


#8

Same here


#9

Same here :slight_smile:


#10

I’m getting the same problem when I try to make a widget. I need help!


#11

works now for me


#12

Same issue for me. I can fix temporarily by creating new keys, I think, but then it comes back. I can log in, but not tweet.


#13

any answers on this?


#14

yes i am also encountering the same problem, i hosted my app on another domain, changed the domain and everything but still getting the error.


#15

I have the same problem too. Can’t even log in! Pls help


#16

can you describe solution


#17

same problem here --started after Jan 14th ---- wordpress post use to tweet automatically (using a plugin) —now the 403 err occurs each time. can do individual tweets ok —but the automatic post >>>> twitter stopped working,


#18

me too im using AI


#20

I have a similar problem, even after resetting my password, it still say the request is understood but is refused. I cannot log in on my blackberry and iPad. Please assist


#21

Could u let us know how u fixed it ?.. Thanks.


#22

I fixed this by making sure I was logged out of twitter