diff options
| author | Ingo Schwarze <schwarze@openbsd.org> | 2014-07-21 15:45:17 +0000 |
|---|---|---|
| committer | Ingo Schwarze <schwarze@openbsd.org> | 2014-07-21 15:45:17 +0000 |
| commit | 5e6a55186f91c0f68c6029281f77e9066dcbe87e (patch) | |
| tree | 7c47c5997f9f3d251b40875f9776af0dcf4e6708 /cgi.h.example | |
| parent | 28d7e7b9d246e8eb2a7500e0f10b1c56e146c901 (diff) | |
| download | mandoc-5e6a55186f91c0f68c6029281f77e9066dcbe87e.tar.gz | |
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.
Diffstat (limited to 'cgi.h.example')
| -rw-r--r-- | cgi.h.example | 3 |
1 files changed, 2 insertions, 1 deletions
diff --git a/cgi.h.example b/cgi.h.example index 4f7273b1..f4c78318 100644 --- a/cgi.h.example +++ b/cgi.h.example @@ -1,8 +1,9 @@ /* Example compile-time configuration file for man.cgi(8). */ +#define HTTP_HOST "mdocml.bsd.lv" #define MAN_DIR "/var/www/man" #define CSS_DIR "" #define CUSTOMIZE_TITLE "Manual pages with mandoc" #define CUSTOMIZE_BEGIN "<H2>\nManual pages with " \ "<A HREF=\"http://mdocml.bsd.lv/\">mandoc</A>\n</H2>" -#define COMPAT_OLDURI Yes +#define COMPAT_OLDURI Yes |