From 5e6a55186f91c0f68c6029281f77e9066dcbe87e Mon Sep 17 00:00:00 2001 From: Ingo Schwarze Date: Mon, 21 Jul 2014 15:45:17 +0000 Subject: Kristaps points out that the current HTTP/1.1 draft standard (RFC 2616) requires the Location: response-header field to be an absolute URI (14.30), and only the most recent proposed standard (RFC 7231), which is barely a month old, allows a relative Location: (7.1.2). While most modern browsers appear to support relative Location: headers, some may not, and it's maybe a bit early to rely on relative Location: headers. I'm not going back to the HTTP_HOST or SERVER_NAME CGI variables, though. While some CGI programs certainly require those, in which case both the CGI programmer and the web server admin have to be very careful to keep the system secure and reliable, man.cgi(8) does not really need them. We always know at compile time which domain we are running for, and for man.cgi(8), security and reliability are definitely much more important than flexibility. So make HTTP_HOST a compile-time definition for now. --- man.cgi.8 | 5 +++++ 1 file changed, 5 insertions(+) (limited to 'man.cgi.8') diff --git a/man.cgi.8 b/man.cgi.8 index 624e0207..169b2ae2 100644 --- a/man.cgi.8 +++ b/man.cgi.8 @@ -189,6 +189,11 @@ element. An ASCII string to be used for the HTML .Aq TITLE element. +.It Ev HTTP_HOST +The FQDN of the (possibly virtual) host the HTTP server is running on. +This is used for +.Ic Location: +headers in HTTP 303 responses. .It Ev MAN_DIR A path to the .Nm -- cgit