Do Dev Tunnels Have an HTTP Timeout Issue?

Question

Do Dev Tunnels Have an HTTP Timeout Issue?

Tony Pitman 81

Using a dev tunnel to connect a Mac client app to an ASP.NET service running on a PC has raised a timeout issue.

One API call takes about 70 seconds to complete, but when the client runs on the Mac via the dev tunnel, an HTTP timeout occurs after 60 seconds. Although the server method completes successfully 10 seconds later, the client disconnects due to the timeout.

In testing, running the client on Windows without the dev tunnel and connecting directly to localhost allows it to wait for the full 70 seconds and receive the successful result.

If the client is run on Windows using the dev tunnel instead of connecting directly to localhost on the dev PC, it also times out after 60 seconds, similar to running the client on the Mac.

It appears that the dev tunnel is causing the timeout at 60 seconds.

Unfortunately I don't have a good way to make the process take less time.

Is there a way to resolve this timeout issue?

Anonymous

2025-01-22T13:22:59.0633333+00:00

Hi @Tony Pitman,

After check the devtunnel github issues, I found a similar issue. And on Apr 23, 2024, we don't plan to add support for extending gateway timeout to devtunnel.

Could you kindly share the timeout error for us ? We need to confirm if it's a same issue.

And your API takes 70 seconds, which is a very bad experience, and if the time is mostly spent reading data, then do you consider using caching related technology, that will save a lot of time.

Best Regards

Jason
Tony Pitman 81 Reputation points

2025-01-22T16:27:31.22+00:00

I understand that 70 seconds is a long time. This is a system that we have decided the time is acceptable and very specific to our process.

As far as the error the response has a reason message of "Bad Request".

At one point while looking into this I think I was a 504, but can't seem to find where I saw that.

What would it take to open this back up and add support for setting the timeout? There are cases where it would be useful especially when debugging as the Issue poster indicated.
Anonymous

2025-01-23T10:53:16.6166667+00:00

Hi @Tony Pitman,

Thanks for contacting us. The github issue tells us on Apr 23, 2024 there are no plans to add the ability to set a timeout.

If you need this feature, you can raise a github issue.

Then our Product Team will reply you soon.

Best Regards

Jason
Alex Bogomolov 35 Reputation points

2025-02-01T19:38:50.5633333+00:00

This is exact issue I encounter currently. My intent is to use devtunnel to share the locally running gradio app to test with the client remotely. However, long running gradio jobs always interrupt the websockets connection to the backend after 60 seconds. Some jobs can take up to 200 seconds to respond or more. Is there any other way to increase this timeout in devtunnel settings?
mehrdad ataee 0 Reputation points

2025-05-11T20:37:13.1066667+00:00

I have the same problem, and it has stopped me from further testing my web app.
I'm trying to run a WebGL build made with unity, which due to its size takes over 60 seconds to load, hence I receive a “net::ERR_HTTP2_PROTOCOL_ERROR 200 (OK)” error.
It would have been much appreciated if you could add a feature to modify the 60 seconds timeout.

1 answer

Your answer

Anonymous

2025-01-22T13:22:59.0633333+00:00

Hi @Tony Pitman,

After check the devtunnel github issues, I found a similar issue. And on Apr 23, 2024, we don't plan to add support for extending gateway timeout to devtunnel.

Could you kindly share the timeout error for us ? We need to confirm if it's a same issue.

And your API takes 70 seconds, which is a very bad experience, and if the time is mostly spent reading data, then do you consider using caching related technology, that will save a lot of time.

Best Regards

Jason
Tony Pitman 81 Reputation points

2025-01-22T16:27:31.22+00:00

I understand that 70 seconds is a long time. This is a system that we have decided the time is acceptable and very specific to our process.

As far as the error the response has a reason message of "Bad Request".

At one point while looking into this I think I was a 504, but can't seem to find where I saw that.

What would it take to open this back up and add support for setting the timeout? There are cases where it would be useful especially when debugging as the Issue poster indicated.
Anonymous

2025-01-23T10:53:16.6166667+00:00

Hi @Tony Pitman,

Thanks for contacting us. The github issue tells us on Apr 23, 2024 there are no plans to add the ability to set a timeout.

If you need this feature, you can raise a github issue.

Then our Product Team will reply you soon.

Best Regards

Jason
Alex Bogomolov 35 Reputation points

2025-02-01T19:38:50.5633333+00:00

This is exact issue I encounter currently. My intent is to use devtunnel to share the locally running gradio app to test with the client remotely. However, long running gradio jobs always interrupt the websockets connection to the backend after 60 seconds. Some jobs can take up to 200 seconds to respond or more. Is there any other way to increase this timeout in devtunnel settings?
mehrdad ataee 0 Reputation points

2025-05-11T20:37:13.1066667+00:00

I have the same problem, and it has stopped me from further testing my web app.
I'm trying to run a WebGL build made with unity, which due to its size takes over 60 seconds to load, hence I receive a “net::ERR_HTTP2_PROTOCOL_ERROR 200 (OK)” error.
It would have been much appreciated if you could add a feature to modify the 60 seconds timeout.

Answer 1

Jack Dang (WICLOUD CORPORATION) 1,020 Microsoft External Staff

Hello @Tony Pitman ,

Thank you for your question regarding HTTP timeouts when using Dev Tunnels to connect a Mac client app to an ASP.NET service hosted on a Windows PC.

Based on your description, you're encountering a timeout issue when making long-running API calls (approximately 70 seconds) through the dev tunnel.

Dev tunnels currently have a fixed timeout limit of 60 seconds. This limit cannot be configured or extended at this time. Therefore, any API call that takes longer than 60 seconds will result in a timeout error.

Here are some recommended workarounds

Optimize the API Call:

Consider using caching or breaking the task into smaller chunks to reduce execution time.

Offload long-running operations to background tasks and return a status or job ID to the client.

Avoid Dev Tunnels for Long-Running Requests:

For development scenarios involving long-running requests, consider using localhost or a local network connection instead of dev tunnels.

Feature Request:

You may submit a feature request on the Visual Studio GitHub repository to support configurable timeout settings.

Hope my recommendations helpful.

Jack Dang (WICLOUD CORPORATION) 1,020 Reputation points Microsoft External Staff

2025-07-09T02:26:25.6433333+00:00

I hope everything is going well on your side! Just checking in to see if my suggestions were useful. Feel free to reach out if there's anything else I can assist with.
Jack Dang (WICLOUD CORPORATION) 1,020 Reputation points Microsoft External Staff

2025-08-11T07:34:29.2433333+00:00

Hi @Tony Pitman ,

Just checking in — I haven’t heard back from you for a while, I hope everything works out as you expected. If you agree with my suggestion, feel free to interact with the system accordingly!

Share via

Do Dev Tunnels Have an HTTP Timeout Issue?

1 answer

Your answer