Only HTTP/1.0 and HTTP/1.1 version requests are currently supported

[hannespreishuber]

get exception Code: generalException
Message: An error occurred sending the request. with followin codee

msgresponse = Await graphClient.Teams("1cccc") _ .Channels("19:bd775xxxxx@thread.skype").Messages _ .Request() _ .AddAsync(ChatMessage)

exact same code works in diffrent project

Windows 11
Visual Studio 22
asp.net webforms vb.net
.net 4.8
graph 4.29 (going to 5 code wont compile)
azrue core 1.42

https://github.com/hannespreishuber/GraphDemovonppedv
default.aspx.vb

[andrueastman]

Hey @hannespreishuber,

Thanks for raising this.

The latest versions of the library do try to perform http calls via HTTP/2, however it looks like you are using a custom http client to create the GraphServiceClient, any chance you have any like if you change this line

https://github.com/hannespreishuber/GraphDemovonppedv/blob/master/GraphDemovonppedv/Default.aspx.vb#L45

to be something like

        Dim _httpClient = GraphClientFactory.Create(authenticationProvider:=Nothing)

This issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for 4 days. It will be closed if no further activity occurs within 3 days of this comment.

[jdew73]

I am also having the same issue when uploading documents to Sharepoint. Anything under 4 MB works fine as long as I set the RequestMessage's version to 1.1. Anything above 4 MB -- where I need to use a LargeFileUploadTask -- returns the "Only HTTP/1.0 and HTTP/1.1 version requests are currently supported" message. If I remove the RequestMessage 1.1 version, I get a general exception. Please advise. This has killed large file uploads in our app without a stitch of our code changing.

Also, note, we can't set the authorizationprovider to nothing -- need to be able to pass the token along to send the document.

[andrueastman]

Hey @jdew73,

Thanks for raising this.
Are you able to provide more information about the SDK version and dotnet Runtime information you are using in you app scenario as well as how the GraphClient is initialized?

[jdew73]

VB.NET Microsoft Graph 4.24.0 .NET Framework 4.7.2 (we just upgraded from 4.6.1, which did work previously with the same code, except we did not have to specify the message version) I have tried two different methods to initialize the GraphClient: #1) client = New Microsoft.Graph.GraphServiceClient(New Microsoft.Graph.DelegateAuthenticationProvider(Function(requestMessage) requestMessage.Headers.Authorization = New AuthenticationHeaderValue("Bearer", token) requestMessage.Version = New Version(1, 1) etc. End Function)) #2) _httpclient = Microsoft.Graph.GraphClientFactory.Create(authenticationProvider:=Nothing) client = New GraphServiceClient(_httpclient) And then set the client.AuthenticationProvider after. Neither works. From: Eastman ***@***.***> Sent: Wednesday, June 8, 2022 5:33 AM To: microsoftgraph/msgraph-sdk-dotnet ***@***.***> Cc: Jason deWit ***@***.***>; Mention ***@***.***> Subject: Re: [microsoftgraph/msgraph-sdk-dotnet] Only HTTP/1.0 and HTTP/1.1 version requests are currently supported (Issue #1367) Hey @jdew73<https://github.com/jdew73>, Thanks for raising this. Are you able to provide more information about the SDK version and dotnet Runtime information you are using in you app scenario as well as how the GraphClient is initialized? — Reply to this email directly, view it on GitHub<#1367 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AMOL42MZM6X27FOX7EMYQILVOBSFZANCNFSM5XVXV6AA>. You are receiving this because you were mentioned.Message ID: ***@***.******@***.***>>

[andrueastman]

Thanks for the extra information.

When using the FileUploadTask, do you notice any difference if you pass the created graphClient in scenario #1 to the to the optional baseClient parameter?

https://github.com/microsoftgraph/msgraph-sdk-dotnet-core/blob/6d23ab70841143b79acaccc3385b2a7d8f351b06/src/Microsoft.Graph.Core/Tasks/LargeFileUploadTask.cs#L36

Also, I would be curious to find out what the result would be if you passed the WinHttpHandler instance explicitly(the SDK should do this for you to prevent the HTTP error) as below.

        Dim authProvider = New DelegateAuthenticationProvider(Function(requestMessage)
                                                                  requestMessage.Headers.Authorization = New AuthenticationHeaderValue("Bearer", token)
                                                              End Function)
        Dim finalHandler = New WinHttpHandler()
        Dim _httpclient = GraphClientFactory.Create(authenticationProvider:=authProvider, finalHandler:=finalHandler)

[jdew73]

At the moment, your first suggestion (the baseClient parameter) looks quite promising. It has worked with a couple of tests. I will do more testing, but I think that did the trick. Thank you. I will post again if I hit a stumbling block. From: Eastman ***@***.***> Sent: Wednesday, June 8, 2022 9:49 AM To: microsoftgraph/msgraph-sdk-dotnet ***@***.***> Cc: Jason deWit ***@***.***>; Mention ***@***.***> Subject: Re: [microsoftgraph/msgraph-sdk-dotnet] Only HTTP/1.0 and HTTP/1.1 version requests are currently supported (Issue #1367) Thanks for the extra information. When using the FileUploadTask, do you notice any difference if you pass the created graphClient in scenario #1<#1> to the to the optional baseClient parameter? https://github.com/microsoftgraph/msgraph-sdk-dotnet-core/blob/6d23ab70841143b79acaccc3385b2a7d8f351b06/src/Microsoft.Graph.Core/Tasks/LargeFileUploadTask.cs#L36 Also, I would be curious to find out what the result would be if you passed the WinHttpHandler instance explicitly(the SDK should do this for you to prevent the HTTP error) as below. Dim authProvider = New DelegateAuthenticationProvider(Function(requestMessage) requestMessage.Headers.Authorization = New AuthenticationHeaderValue("Bearer", token) End Function) Dim finalHandler = New WinHttpHandler() Dim _httpclient = GraphClientFactory.Create(authenticationProvider:=authProvider, finalHandler:=finalHandler) — Reply to this email directly, view it on GitHub<#1367 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AMOL42MRLNF22LYBUKX5KXTVOCQDFANCNFSM5XVXV6AA>. You are receiving this because you were mentioned.Message ID: ***@***.******@***.***>>