Pooya Parsa
Pooya Parsa
I am wondering if we can alternatively support `before:[validate()]` to allow multiple validate functions and avoid adding new hook.
It makes sense for type complexity I am thinking it could give some overhead for when we want to do body normalization, we actually read the body (and an external...
Update: Both me and @danielroe need to rethink about whole typing and validation and how it works with downstream (Nitro and Nuxt) types and best type/runtime safely+perf balance which is...
(closing as object syntax removed, we need to build it based on new middleware format)
Link to docs/spec?
/cc @danielroe I think you might be the best to check this when had time 🙏🏼
Interesting approach. I think it can lift up 4k per cookie size by browsers. But we have to also consider overall headers size by servers is usually also limited (i...
We have `getRequestHost({ xForwardedHost: true })`. Main benefit of using utils for each semi-standard header likt this is that we can support other vendor header as same name. How do...
I am up to supporting a special event context property such as `event.context.isTrustedProxy` to automatically enable headers detection however it should be user responsibility solely to write logic. Based on...
Thanks for explaining your use cases. I think it makes sense to introduce a standard context flag down the line from h3 directly so that the ecosystem (nitro, nuxt, nuxt...