LinqToTwitter Work Item Rss Feed

Commented Unassigned: Conflict between LinqToTwitter Gzip requests and default GZip requests [32553]

JoeMayo — Wed, 15 May 2013 16:44:30 GMT

Hi,

There is an small conflict between the GZip logic for built-in in LinqToTwitter and the registered WebRequest creators. Mainly if they handle GZip.

The default Creator is WebRequestCreator.BrowserHttp (http://msdn.microsoft.com/en-us/library/system.net.browser.webrequestcreator.browserhttp(v=vs.95).aspx) can be overwritten once by a class that implements IWebRequestCreate (http://msdn.microsoft.com/en-us/library/system.net.iwebrequestcreate(v=vs.110).aspx) by using the method WebRequest.RegisterPrefix (WebRequest.RegisterPrefix). By doing this, then all the requests of the application will use the given handler.

In particular, my sample app registers a WebCreators from a third party lib ( https://github.com/dotMorten/SharpGIS.GZipWebClient ) which we have been using since all the requests are GZip compressed.

private void Application_Launching(object sender, LaunchingEventArgs e)
{
WebRequest.RegisterPrefix("http://", SharpGIS.WebRequestCreator.GZip);
WebRequest.RegisterPrefix("https://", SharpGIS.WebRequestCreator.GZip);
}

By setting the previous code in my app, the following code stops working properly (regardless I set UseCompression to false or true):

_pinAuthorizer = new PinAuthorizer
{
Credentials = new InMemoryCredentials
{
ConsumerKey = TwitterApiClient.Instance.ConsumerKey,
ConsumerSecret = TwitterApiClient.Instance.ConsumerSecret
},
UseCompression = true,
GoToTwitterAuthorization = pageLink => Dispatcher.BeginInvoke(() => OAuthWebBrowser.Navigate(new Uri(pageLink, UriKind.Absolute)))
};

A quick workaround is to implement the IWebRequestCreate in a custom class and set it up as request creator. This custom class will use the default RequestCreator for any request to twitter and all other requests can use the GZipWebRequestCreator.

Attached is the project sample for you to check.
Regards,
Herber
Comments: Thanks. Joe

Created Unassigned: Conflict between LinqToTwitter Gzip requests and default GZip requests [32553]

hmadrigal — Wed, 15 May 2013 16:12:08 GMT

Closed Unassigned: OAuth_Verifier header not sent during asynchronous verification [32552]

JoeMayo — Mon, 13 May 2013 20:18:54 GMT

I'm using a PIN Authorizer in a WPF application.

I'm currently displaying the page link i get in my GoToTwitterAuthorization callback in an embedded wpf webbrowser control and calling BeginAuthorize on the pin authorizer. When I call CompleteAuthorize on the pin authorizer passing in the pin, I get a 401 back. Using Fiddler I grabbed the request header and it looks like this

```
GET https://api.twitter.com/oauth/access_token HTTP/1.1
Authorization: OAuth oauth_callback="oob",oauth_consumer_key="<removed>",oauth_nonce="659810",oauth_signature_method="HMAC-SHA1",oauth_timestamp="1368457219",oauth_token="2JTvw9nh7uagYfEk1VKrEqLS6hkjVoE2ifPygCdjQ",oauth_version="1.0",oauth_signature="NNrxwVToX2MM0o5mQ194NRx1vWg%3D"
Accept-Encoding: deflate,gzip
Host: api.twitter.com

```

and here's the response

```
<?xml version="1.0" encoding="UTF-8"?>
<hash>
<error>Required oauth_verifier parameter not provided</error>
<request>/oauth/access_token</request>
</hash>
```

If I rejigger my code to work with a call to pinAuthorizer.Authorize() and using an external browser everything works correctly.

Commented Unassigned: OAuth_Verifier header not sent during asynchronous verification [32552]

JoeMayo — Mon, 13 May 2013 19:57:51 GMT

Commented Unassigned: OAuth_Verifier header not sent during asynchronous verification [32552]

jmpinchot — Mon, 13 May 2013 19:33:46 GMT

Commented Unassigned: OAuth_Verifier header not sent during asynchronous verification [32552]

jmpinchot — Mon, 13 May 2013 19:12:03 GMT

Commented Unassigned: OAuth_Verifier header not sent during asynchronous verification [32552]

JoeMayo — Mon, 13 May 2013 18:38:55 GMT

Commented Unassigned: OAuth_Verifier header not sent during asynchronous verification [32552]

jmpinchot — Mon, 13 May 2013 18:09:34 GMT

Commented Unassigned: OAuth_Verifier header not sent during asynchronous verification [32552]

JoeMayo — Mon, 13 May 2013 17:50:55 GMT

Created Unassigned: OAuth_Verifier header not sent during asynchronous verification [32552]

jmpinchot — Mon, 13 May 2013 15:05:12 GMT

Closed Unassigned: ArgumentNullException when call TweetWithMedia with empty string as status on Windows Phone [32551]

JoeMayo — Wed, 01 May 2013 18:08:38 GMT

As the title

Commented Unassigned: ArgumentNullException when call TweetWithMedia with empty string as status on Windows Phone [32551]

JoeMayo — Wed, 01 May 2013 18:08:13 GMT

As the title
Comments: This is by design. The Twitter API's [documentation for update_with_media](https://dev.twitter.com/docs/api/1.1/post/statuses/update_with_media) states that status is required. Therefore, LINQ to Twitter is telling you this early on. If you view the Message property of the exception, you should read "status is a required parameter".

Created Unassigned: ArgumentNullException when call TweetWithMedia with empty string as status on Windows Phone [32551]

AgileHobo — Wed, 01 May 2013 17:04:16 GMT

As the title

Closed Unassigned: Windows 8 oAuth Demo fails with 401 Unauthorized [32550]

JoeMayo — Sun, 28 Apr 2013 22:43:27 GMT

Commented Unassigned: Windows 8 oAuth Demo fails with 401 Unauthorized [32550]

adamtuliper — Fri, 26 Apr 2013 07:45:28 GMT

I've set the ConsumerKey and ConsumerSecret with those provisioned to me by Twitter.

I get "The remote server returned an error: (401) Unauthorized." on the await line below in Win8OAuthDemo\TweetPage.xaml.cs

if (auth == null || !auth.IsAuthorized)
{
await auth.AuthorizeAsync();
}

Comments: Resolved: On dev.twitter.com set the callback to http://application.local (it was none) and in the source set Callback = Windows.Security.Authentication.Web.WebAuthenticationBroker.GetCurrentApplicationCallbackUri(),

Commented Unassigned: Windows 8 oAuth Demo fails with 401 Unauthorized [32550]

adamtuliper — Thu, 25 Apr 2013 07:47:39 GMT

I've set the ConsumerKey and ConsumerSecret with those provisioned to me by Twitter.

I get "The remote server returned an error: (401) Unauthorized." on the await line below in Win8OAuthDemo\TweetPage.xaml.cs

if (auth == null || !auth.IsAuthorized)
{
await auth.AuthorizeAsync();
}

Comments: Its late and I should read the Twitter Error message better returned in Fiddler. The issue would be to change the demo source code from Callback = new Uri("http://linqtotwitter.codeplex.com/"), to Callback = new Uri("oob"), however "oob" is not a valid Uri and thus an exception is thrown when you try that. Does this require a code change to Linq To Twitter?

Commented Unassigned: Windows 8 oAuth Demo fails with 401 Unauthorized [32550]

adamtuliper — Thu, 25 Apr 2013 07:41:18 GMT

I've set the ConsumerKey and ConsumerSecret with those provisioned to me by Twitter.

I get "The remote server returned an error: (401) Unauthorized." on the await line below in Win8OAuthDemo\TweetPage.xaml.cs

if (auth == null || !auth.IsAuthorized)
{
await auth.AuthorizeAsync();
}

Comments: Additional info - the response from Twitter is: <error>Desktop applications only support the oauth_callback value 'oob'</error> I've tried the default Callback = new Uri("http://linqtotwitter.codeplex.com/") as well as using the following which works in WinJS when doing oAuth 'manually' Windows.Security.Authentication.Web.WebAuthenticationBroker.GetCurrentApplicationCallbackUri();

Created Unassigned: Windows 8 oAuth Demo fails with 401 Unauthorized [32550]

adamtuliper — Thu, 25 Apr 2013 07:36:31 GMT

Closed Issue: Support for StallWarnings? [32547]

JoeMayo — Mon, 22 Apr 2013 03:17:59 GMT

I see that a parameter called StallWarnings is listed in streaming documentation as a parameter to the listen query, which is intended to warn the client they are falling behind and may be disconnected.

But, this parameter doesn't seem to be available (as of version 2.1.04). Is this unintentionally omitted or am I missing something?

Comments: Added StallWarnings and other parameters to all streams.

Created Unassigned: Error posting tweets with larger photos (below 3MB) [32549]

JoeMayo — Thu, 11 Apr 2013 17:56:04 GMT

A web application similar to Hootsuites posting functionality.
Not a mobile application.