- 30 Jul, 2015 4 commits
-
-
Jacob Vosmaer authored
-
Jacob Vosmaer authored
-
Jacob Vosmaer authored
-
Jacob Vosmaer authored
-
- 29 Jul, 2015 7 commits
-
-
Jacob Vosmaer authored
-
Jacob Vosmaer authored
-
Jacob Vosmaer authored
-
Jacob Vosmaer authored
-
Jacob Vosmaer authored
-
Jacob Vosmaer authored
-
Jacob Vosmaer authored
Support for gitlab-git-http-server got merged upstream: https://gitlab.com/gitlab-org/gitlab-ce/commit/d64ae5363fc17bf5592bc1a66a53763ddb9a3acc
-
- 28 Jul, 2015 6 commits
-
-
Jacob Vosmaer authored
-
Jacob Vosmaer authored
-
Jacob Vosmaer authored
Supposedly they are not idiomatic!
-
Jacob Vosmaer authored
-
Jacob Vosmaer authored
-
Jacob Vosmaer authored
-
- 27 Jul, 2015 7 commits
-
-
Jacob Vosmaer authored
-
Jacob Vosmaer authored
-
Jacob Vosmaer authored
-
Jacob Vosmaer authored
-
Jacob Vosmaer authored
-
Jacob Vosmaer authored
-
Jacob Vosmaer authored
-
- 25 Jul, 2015 2 commits
-
-
Jacob Vosmaer authored
-
Jacob Vosmaer authored
-
- 26 Jul, 2015 14 commits
-
-
Jacob Vosmaer authored
-
Jacob Vosmaer authored
-
Jacob Vosmaer authored
-
Jacob Vosmaer authored
-
Jacob Vosmaer authored
The path must exist and not contain '/../' (traversal).
-
Jacob Vosmaer authored
I am no 100% sure but I think we can only write the HTTP status code once. So once the 200 is out, we might as well panic on errors. The Go HTTP server will only let the goroutine crash, not the entire server process.
-
Jacob Vosmaer authored
-
Jacob Vosmaer authored
-
Jacob Vosmaer authored
-
Jacob Vosmaer authored
-
Jacob Vosmaer authored
-
Jacob Vosmaer authored
-
Jacob Vosmaer authored
-
Jacob Vosmaer authored
-