Hello Appwrite Community,
I set the timeout to 15 seconds on Appwrite Cloud, but the result still shows 5 seconds. Is this a bug or is it intended?
Kind Regards, Marius
Are you running it in async?
Hey there 👋 Keep alive timeout is a geader for browsers to know when to hang up a request I believe. Appwtite isnt touching any headers so you have full freedom in what you build. My guess would be that this header comes vy default in http server library that we used to build runtime you are using.
To change this number, in res.send or res.json you can send 3rd parameter, which is object of all response headers you want and their values.
Timeout in function settings more connected to internal communication itself - allows you to ensure max durstion if 1 execution to let you better control usage (will be very useful when pricing is introduced on cloud)
Yes it runs in async, is this correct?
As Matej explained, the timeout being shown in the browser is not at all the function timeout
Thank you. Please mark as solved!
Btw, you can edit the title of your posts as well
[SOLVED] Timeout not applied correctly
Recommended threads
- fastly error
Hey! I'm hitting a Fastly error on the www version of our site, but the root domain works fine. We have a wildcard set up, so I expected the subdomain to be cov...
- Facebook's scraper facebookexternalhit g...
share.bardbliss.com but works fine on the raw fra.appwrite.run URL. No execution logs appear when Facebook hits the custom domain. This was working before. How ...
- How to Display File in Web?
I'm trying to use Appwrite's Storage to store images and display them in my app, however when I use the `getFileView`, `getFileDownload` or `getFilePreview` met...