Comments (3)
It is already implemented in the context.request.body()
. It handles JSON, urlencoded, and text automatically. It will handle multipart in the future.
From the README:
.body()
The method resolves to a parsed version of the request body. Currently oak
supports request body types of JSON, text and URL encoded form data. If the
content type of the request is not supported, the request will be rejected
with a 415 HTTP Error.If the content type is supported, the method resolves with an object which
contains atype
property set to"json"
,"text"
,"form"
, or
"undefined"
and avalue
property set with the parsed value of the
property. For JSON it will be the parsed value of the JSON string. For text,
it will simply be a string and for a form, it will be an instance of
URLSearchParams
. For an undefined body, the value will beundefined
.For more advanced use cases of the body, the original server request is
available and contains a.body()
and.bodyStream()
methods.
from oak.
How to
Get body from json and urlencoded
I use .body({type:'form'}) . This work for content type form but not work for content type json?
My console request body is null value ?
Give me example code request body in OAK?
from oak.
Is there body-parser in OAK?
Like body-parser in express Js?
from oak.
Related Issues (20)
- Typo in README.md
- Use body and relay it via proxy middleware in oak v13+ HOT 1
- Proxied request secure?
- Controllers, why doesn't possible inject with private?
- More typing on Request and Response object? HOT 4
- request.body.text() causes error on localhost HOT 3
- Oak import causes a compiled app to hang HOT 1
- context.request.body is not a function
- How to gracefully exit, when Bun Server does not adhere to AbortSignal? HOT 2
- ctx.request.body is not a function
- Application's State type error HOT 2
- A better way to handle pre-processed bodies by zod / joi / yup / ajv
- Use `:authority` psueod-header on HTTP/2 if available HOT 4
- Support `Forwarded` header as well as `X-Forwarded-*` HOT 1
- Exceptions from AsyncGenerator responses cause the connection to hang HOT 2
- `deno emit` does not support dynamic imports and npm dependencies so can't be used with oak HOT 1
- Error handling doesn't work HOT 8
- Body limit in oak@13+ HOT 1
- Property `Context.Params` does not exist HOT 1
- Property Context.Params does not exist HOT 2
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from oak.