Kentaro Suzuki
Kentaro Suzuki
@yusukebe I have created a repository contains a minimal reproduction code and a detailed explanation of the cause. https://github.com/sushichan044/hono-header-handling The explanation may be complicated, but would you please read it...
I think there are two ways to fix this. First, special handling of `content-type` in this branch would be an ad hoc approach. https://github.com/honojs/hono/blob/5ca6c6ef867e022671b4c429c04d0ff89ed0c37c/src/context.ts#L670-L676 Specifically, if `Context.#headers` already contains `content-type`,...
Another approach would be to change the way response headers are stored to make the structure less prone to unexpected overwrites. However, I have no specific idea yet. I think...
In addition, I will document the differences between the two methods of editing headers, `c.header` and `c.res.headers`. Or perhaps we should create a best practice guide when implementing Middlewares 🤔
TODO: refine test case and push
TODO: handle ReDoS
I have a draft implementation that seems to be working.
@sverweij I uploaded an untested implementation to #1009. Testing will take some time, but I'll notify you when it's ready for review!
@yusukebe @resYuto I’m investigating this issue, and I found the following puzzling behavior. ```ts import { Hono } from 'hono' import { showRoutes } from 'hono/dev' const routes = new...
I have an idea for a solution that should work while still supporting the ability to omit path specifications in [chained routes](https://hono.dev/docs/api/routing#chained-route). If it looks working, I’ll open a draft...