-
Notifications
You must be signed in to change notification settings - Fork 4.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Httpclient perfectly work on 3.1 but timeout in .net 5 #47267
Comments
Tagging subscribers to this area: @dotnet/ncl Issue DetailsDescribe the bugI made a project on Asp.net Core 3.1 which is automatically fetching some information from another API (which is only accessible using VPN client) it's work perfectly. Now I converted my project to .net 5 suddenly I am unable to get a response from that API. giving flowing error every time.
HEADERSConnection: keep-alive I tried everything but the result is the same. (Not working)
for another try, I created another test project from scratch in asp.net core 3.1 and it's working. Other info
|
This is most likely related to #44686, sharing the same root cause. .NET 5 switched to use dual-stack sockets for Can you please try the workaround in #44686 (comment)? Also: if you could provide some info about IPV6 support in your VPN environment, it would be very helpful for us to triage the issue. |
After a quick google search for "pulse secure IPV6" I found this: @NitishGawde do you think you are hitting any of the limitations listed there? |
#44686 (Comment) working for me. I think the problem is a dule socket. |
This workaround is not sufficient for users who don't have direct control over their @NitishGawde I'm wondering if you can help us by trying to get more info about why doesn't dual-stack work in your VPN. (Maybe by asking your IT department?) I'm happy to contact you privately if it's better for you. |
@NitishGawde will you be able to help us gather more info about your environment? |
@karelz and @antonfirsov what information do you need from my end. |
@NitishGawde we need to understand why dual-sockets are not working correctly in your environment -- is it VPN misconfiguration? Old version? Or is that by design in your VPN client? (known limitation) |
Triage: seems like workaround worked. There's nothing actionable at the moment, closing. |
Describe the bug
I made a project on Asp.net Core 3.1 which is automatically fetching some information from another API (which is only accessible using VPN client) it's work perfectly.
Now I converted my project to .net 5 suddenly I am unable to get a response from that API.
giving flowing error every time.
I tried everything but the result is the same. (Not working)
1.
for another try, I created another test project from scratch in asp.net core 3.1 and it's working.
and another same project created in asp.net core 5 it's not working.
VPN Client info
Other info
I am not getting ping from the server where API is hot because of the VPN client.
but it's perfectly working on Asp.net core 3.1, In browser, and POSTMAN also but not in .net 5
The text was updated successfully, but these errors were encountered: