go-safeweb
go-safeweb copied to clipboard
Secure-by-default HTTP servers in Go.
A nice feature of http.Mux is that it can be used as a handler, so users can set up separate parts of an application on separate muxes that share a...
On this PR: https://github.com/google/go-safeweb/runs/4009332391?check_suite_focus=true I get: ``` Run [ "$(gofmt -l $(find . -name '*.go') 2>&1)" = "" ] [ "$(gofmt -l $(find . -name '*.go') 2>&1)" = "" ]...
Status badges with the following information: - Github Actions Go status - Go Report - Go Reference - License
Fixes #292 > Implemented contributing file and instructions on `README.md`
We should have an octet-stream response that just copies from a given Reader. This would consist in adding a new case to the [`DefaultDispatcher`](https://github.com/google/go-safeweb/blob/master/safehttp/default_dispatcher.go#L43) and implement a new type that...
Assess the need for `safehttp.Map` and potentially remove it.
Currently, interceptors can only know what happened before the `Dispatcher` has run. In particular, any kind of time measurements or status code logging is impossible.
We should reserve some characters to support path parameters in the future. I propose to reserve `$` as a trigger for path parameters. Examples: * `/users/$id:int/page`: this parses the ID...