qiangxue/fasthttp-routing

A fast and powerful routing package for fasthttp servers

fasthttp-routing's Issues

fasthttp-routing not writing user set headers on user handler error

As I pointed here the fasthttp-routing uses builtin Error() function of fasthttp.RequestCtx in it's handler (file report.go lines 103 and 105). This function however completely resets response which introduces problem e.g. when returning error 401 (it should return header WWW-Authenticate in response and resetting response deletes all headers). Would it be possible to implement custom error handling function which would correctly print all user-set headers in response on error encounter?

希望能增加域名绑定支持

@qiangxue

你好，我发现目前route没有绑定指定域名的方法，想请教一下是否有考虑过支持呢
或者有什么能够自定义的方法吗？谢谢

cors

What could I be doing wrong?

	router := routing.New()

	router.Use(func(req *routing.Context) error {
		origin := string(req.Request.Header.Peek("Origin"))
		if origin == "" {
			origin = "*"
		}

		req.Response.Header.Set("Access-Control-Allow-Origin", origin)
		req.Response.Header.Set("Access-Control-Allow-Credentials", "true")
		req.Response.Header.Set("Access-Control-Allow-Methods", "GET,HEAD,PUT,POST,DELETE")
		req.Response.Header.Set("Access-Control-Allow-Headers", "Accept, Content-Type, Content-Length, Accept-Encoding, X-CSRF-Token, Authorization")

		return nil
	})

How to get named route path only?

I'm using router.Route("route name") method to get the path of the named route. As I understand it returns a &Route struct but path field is not accessible because not exported.

I like this function because is useful for reverse routing.

Is possible to get the path from named route?

NotFoundHandler can't write 404 status code and message

func NotFoundHandler(ctx *routing.Context) error {
ctx.WriteString("Not Found:" + strconv.Itoa(http.StatusNotFound))
ctx.Response.SetStatusCode(http.StatusNotFound)
return routing.NewHTTPError(http.StatusNotFound)
}

Could you advise how to select ozzo-routing or fasthttp-routing?

Could you advise why not use fasthttp-routing to replace ozzo-routing in your ozzo framework if it is extremely fast?
Thanks.