pjg711 / oauth-php

Automatically exported from code.google.com/p/oauth-php
MIT License
0 stars 0 forks source link

Bad error message #75

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago
What steps will reproduce the problem?

>>> Any access to OAuthRequester::requestAccessToken() that results in an 
execption thrown due to empty text or code different of 200.

What is the expected output? What do you see instead?

>>> First exception throw:
Expected: No answer from the server <uri> while requesting an access token
Seen: No answer from the server <uri> while requesting a request token

>>> Second exception throw:

Expected: Unexpected result from the server <uri> (<code>) while requesting an 
access token
Seen: Unexpected result from the server <uri> (<code>) while requesting a 
request token

What version of the product are you using? On what operating system?

>>> version: @version $Id: OAuthRequester.php 134 2010-06-22 17:00:32Z 
brunobg@corollarium.com
>>> OS: Windows 2008 Server

Please provide any additional information below.

>>> No further information needed IMO. I appreciate your attention.

Original issue reported on code.google.com by pesadelo...@gmail.com on 10 Nov 2010 at 11:29

GoogleCodeExporter commented 8 years ago
[deleted comment]
GoogleCodeExporter commented 8 years ago
Sorry. Due to a link malfunction, I ended posting 4 extra copies of the entry 
above. Please, remove them.

Thanks.

Original comment by pesadelo...@gmail.com on 11 Nov 2010 at 3:05

GoogleCodeExporter commented 8 years ago

Original comment by fiedler....@gmail.com on 17 Nov 2010 at 8:38

GoogleCodeExporter commented 8 years ago
Hi, I don't understand exactly your bug... If $text is empty or a code != 200 
is returned, an exception is supposed to be returned. 

Original comment by brunobg%...@gtempaccount.com on 17 Nov 2010 at 5:10

GoogleCodeExporter commented 8 years ago
Oh, I see, it was the error message that was wrong :) 

Easiest bug fix ever, on r166. Thanks a lot!

Original comment by brunobg%...@gtempaccount.com on 17 Nov 2010 at 5:11

GoogleCodeExporter commented 8 years ago
LOL, I should have ignored the message template and writen just "the error 
message is wrong in the lines <x> and <y>".

Thank you for the quick fix.

Original comment by pesadelo...@gmail.com on 17 Nov 2010 at 5:21