This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(118.4, 27%, 21%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ETP%3C/text%3E%3C/svg%3E)
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?
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
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.
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