]> gitweb.ps.run Git - ps-cgit/commit
projects / ps-cgit / commit
? search:
summary | shortlog | log | commit | commitdiff | tree
(parent: c641e0a) | patch
Return proper HTTP response when accessing info/
authorLukas Fleischer <cgit@cryptocrack.de>
Thu, 15 Jan 2015 18:47:42 +0000 (19:47 +0100)
committerJason A. Donenfeld <Jason@zx2c4.com>
Thu, 15 Jan 2015 18:48:44 +0000 (19:48 +0100)
commited7e3bc822856c30066a4ff0178033b22046fe96
treed0cfb14346d8f14f5dbb0ae75fe5071013666b19tree | snapshot
parentc641e0ab64f447cd39c6d5737fd498ace3ed8735commit | diff
Return proper HTTP response when accessing info/

Currently, when a user directly accesses the info command of a
repository, we exit cgit without printing anything to stdout, bringing
up error messages like "502 Bad Gateway" or "An error occurred while
reading CGI reply (no response received)". Instead of bailing out, at
least print the HTTP headers, including a reasonable error message.

Reported-by: Janus Troelsen
Signed-off-by: Lukas Fleischer <cgit@cryptocrack.de>
ui-clone.c diff | blob | history
Unnamed repository; edit this file 'description' to name the repository.