The reason is because normally filters are only ap...

# http4k

[dave]

The reason is because normally filters are only applied AFTER you match (in a routing context)

[Razvan]

Is what I was supposing, so adding an OPTIONS route like
in app if I add routes(...,PATH bind OPTIONS to {Response(OK)} should fix it ? or should

[dave]

no - that's already handled by the CORs filter - if you want it to be handled automatically, encapsulate your routing handler as an HttpHandler reference and then apply the Cors filter to that.