CORS middleware: Possible to make OPTIONS handling optional?

[alvinsw]

Does the CORS specification mandates that the HTTP OPTIONS method to be handled in a specific way?

hono/src/middleware/cors/index.ts

Line 113 in eb86162

if (c.req.method === 'OPTIONS') {

Can we make that behavior optional by adding all the required headers before the await next() and returning a default 204 response after the await next() only if no response has been sent by the previous route handlers?

[yusukebe]

Hi @alvinsw

You may do it with custom middleware. But, though I've tried, I haven't found a good way right now.

[alvinsw]

What is the best way to "wrap" another middleware with our own custom middleware? Can you give a code example?

[tclohm]

Here is how I would wrap another middleware,

const custom: MiddlewareHandler = async (c, next) => {
  console.log('Inside')
  await next()
}

const wrap = (middleware: MiddlewareHandler): MiddlewareHandler => {
  return async (c, next) => {
    console.log('Before')
    await middleware(c, next)
    console.log('After')
  }
}

app.use('/', wrap(custom))

Hope that helps