Lukas Fleischer ed7e3bc822 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>

2015-01-15 19:48:44 +01:00

2.2 KiB

Raw Blame History

View Raw