Re^3: Understanding oAuth with Perl

I see in http://cpansearch.perl.org/src/SIMONW/Net-OAuth-Simple-1.5/lib/Net/OAuth/Simple.pm

    return $self->_error("$method on $request failed: ".$response->sta
+tus_line)
      unless ( $response->is_success );
[download]

3xx is not a 2xx, so is_success of HTTP::Status fails.

According to http://en.wikipedia.org/wiki/HTTP_302/http://en.wikipedia.org/wiki/HTTP_303, 303 is the appropriate response for a successful post, but most apps still use 302 erroneously

So, barring an actual error (follow the redirect), Net::Oauth::Simple needs a patch, yammer needs a patch

Comment on Re^3: Understanding oAuth with Perl Download Code

Replies are listed 'Best First'.
Re^4: Understanding oAuth with Perl by Anonymous Monk on Mar 10, 2011 at 13:25 UTC
After checking https://www.yammer.com/api_doc.html#resources_messages_manipulating When posting a new message, the response body will include the new message formatted as in message polling above. This allows you to immediately display the newly-posted message back to the user. I think its a bug that the api_doc doesn't explicitly list what type of status code the response should have, like it does for many other methods. I think you definitely need to check the content, maybe as per LWP::Debug? `$app->{browser}->add_handler("response_done", sub { shift->dump; retur +n });` [download] Or maybe with `->SUPER::new( tokens => \%tokens, browser => WWW::Mechanize->new( autocheck => 0 ), )` [download] and then you can `my $response = eval { $app->view_restricted_resource ... }; unless( $response ){ warn "ERROR $@ "; $response = $app->res; # WWW::Mechanize cache it for you } print $response->content;` [download] or something like that	[reply] [d/l] [select]

Replies are listed 'Best First'.

Re^4: Understanding oAuth with Perl
by Anonymous Monk on Mar 10, 2011 at 13:25 UTC

https://www.yammer.com/api_doc.html#resources_messages_manipulating: When posting a new message, the response body will include the new message formatted as in message polling above. This allows you to immediately display the newly-posted message back to the user.

I think you definitely need to check the content, maybe as per LWP::Debug?

$app->{browser}->add_handler("response_done", sub { shift->dump; retur
+n });
[download]

Or maybe with


->SUPER::new(
    tokens => \%tokens, 
    browser => WWW::Mechanize->new( autocheck => 0 ),
)
[download]

  my $response = eval { $app->view_restricted_resource ... };
  unless( $response ){
    warn "ERROR $@ ";
    $response = $app->res; # WWW::Mechanize cache it for you
  }
  print  $response->content;
[download]

[reply]
[d/l]
[select]