dima/supabase
1
0 Fork 0
mirror of https://github.com/supabase/supabase.git synced 2026-10-11 12:25:05 +03:00
Code Issues Packages Projects Releases Wiki Activity

Merge pull request #9844 from supabase/laktek-patch-3

Browse Source 
Add a suggestion on using HTTP Methods
This commit is contained in:
Lakshan Perera authored and GitHub committed 2022-10-26 07:47:03 +11:00
2 parents 673ac9e9d7 00ead8d279
commit 4f0b4ecb17
1 file changed
+4 -1
Download Patch File Download Diff File Expand all files Collapse all files
apps/reference/docs/guides/functions.mdx
+4 -1
View File
@@ -263,6 +263,10 @@ serve(async (req) => {
})
```
### Using HTTP Methods
Edge Functions supports `GET`, `POST`, `PUT`, `PATCH`, `DELETE`, and `OPTIONS`. A function can be designed to perform different actions based on a request's HTTP method. See the [example on building a RESTful service](https://github.com/supabase/supabase/tree/master/examples/edge-functions/supabase/functions/restful-tasks) to learn how to handle different HTTP methods in your function.
## Limitations
- Deno Deploy limitations
@@ -270,5 +274,4 @@ serve(async (req) => {
- Cannot write to File System
- Edge Functions
- Local development - only one function at a time
- Supabase Functions only supports `POST`, `OPTIONS`, and `GET` requests.
- Serving of HTML content is not supported (`GET` requests that return `text/html` will be rewritten to `text/plain`).