Sync with IANA Status Code Registry

From https://www.iana.org/assignments/http-status-codes/http-status-codes.xhtml

OK sthen@ miod@

Use the original requested URI for REQUEST_URI.

ok millert florian

Set the REQUEST_URI CGI variable to the requested URI and query string
instead of the rewritten path and query string.

Patch from Tim Baumgard, reminded by Mischa Peters.

ok benno, reyk

sync http.h with relayd
ok reyk@

Use "compliant" header guards by avoiding the reserved '_' namespace.

Pointed out by Markus Elfring

OK mikeb@ millert@

More http status codes.
OK benno@, reyk@

bump copyright year

SVG is common enough to add it to the default types.

whitespace spotted while studying the code

Add various RFC-based WebDAV methods to the list of accepted HTTP methods.
This fixes (Fast)CGI-based WebDAV and CalDAV (calendar) servers with httpd.

ok benno@ stsp@

Sync with RFC 7230-7235 phrases and IANA registered status codes.

ok reyk@

When opening directories, re-match the location after the index file
has been appended. This allows to use a fastcgi target as the default
index, for example index.php.

OK florian@

branches: 1.5.2;
Allocate http_host instead of carrying a buffer in the descriptor.

It is recommended to use a URL in the Location header of 3xx
responses. To accomplish this, add some semantics to retrieve the
server host name of a connection: either IP, IP:PORT (if not 80) or
[IP6]:PORT, or Host value (if valid).

Sync file to be identical in relayd(8) and httpd(8).

Add support for media types (aka. MIME types): the types section is
compatible to nginx' mime.types file which can be included directly.
If not present, use a few built-in defaults for html, css, txt, jpeg,
gif, png, and js.

Add httpd(8), an attempt to turn the relayd(8) codebase into a simple
web server. It is not finished yet and I just started it today, but
the goal is to provide an HTTP server that a) provides minimal
features, b) serves static files, c) provides FastCGI support, and d)
follows common coding practices of OpenBSD.

It will neither support plugins, nor custom memory allocators, EBCDIC
support, PCRE or any other things that can be found elsewhere.
httpd(8) is not intended to provide a fully-featured replacement for
nginx(8) or the Apache, but it will provide enough functionality that
is needed in the OpenBSD base system.

ok deraadt@

Use the original requested URI for REQUEST_URI.

ok millert florian

Set the REQUEST_URI CGI variable to the requested URI and query string
instead of the rewritten path and query string.

Patch from Tim Baumgard, reminded by Mischa Peters.

ok benno, reyk

sync http.h with relayd
ok reyk@

Use "compliant" header guards by avoiding the reserved '_' namespace.

Pointed out by Markus Elfring

OK mikeb@ millert@

More http status codes.
OK benno@, reyk@

bump copyright year

SVG is common enough to add it to the default types.

whitespace spotted while studying the code

Add various RFC-based WebDAV methods to the list of accepted HTTP methods.
This fixes (Fast)CGI-based WebDAV and CalDAV (calendar) servers with httpd.

ok benno@ stsp@

Sync with RFC 7230-7235 phrases and IANA registered status codes.

ok reyk@

When opening directories, re-match the location after the index file
has been appended. This allows to use a fastcgi target as the default
index, for example index.php.

OK florian@

branches: 1.5.2;
Allocate http_host instead of carrying a buffer in the descriptor.

It is recommended to use a URL in the Location header of 3xx
responses. To accomplish this, add some semantics to retrieve the
server host name of a connection: either IP, IP:PORT (if not 80) or
[IP6]:PORT, or Host value (if valid).

Sync file to be identical in relayd(8) and httpd(8).

Add support for media types (aka. MIME types): the types section is
compatible to nginx' mime.types file which can be included directly.
If not present, use a few built-in defaults for html, css, txt, jpeg,
gif, png, and js.

Add httpd(8), an attempt to turn the relayd(8) codebase into a simple
web server. It is not finished yet and I just started it today, but
the goal is to provide an HTTP server that a) provides minimal
features, b) serves static files, c) provides FastCGI support, and d)
follows common coding practices of OpenBSD.

It will neither support plugins, nor custom memory allocators, EBCDIC
support, PCRE or any other things that can be found elsewhere.
httpd(8) is not intended to provide a fully-featured replacement for
nginx(8) or the Apache, but it will provide enough functionality that
is needed in the OpenBSD base system.

ok deraadt@

Set the REQUEST_URI CGI variable to the requested URI and query string
instead of the rewritten path and query string.

Patch from Tim Baumgard, reminded by Mischa Peters.

ok benno, reyk

sync http.h with relayd
ok reyk@

Use "compliant" header guards by avoiding the reserved '_' namespace.

Pointed out by Markus Elfring

OK mikeb@ millert@

More http status codes.
OK benno@, reyk@

bump copyright year

SVG is common enough to add it to the default types.

whitespace spotted while studying the code

Add various RFC-based WebDAV methods to the list of accepted HTTP methods.
This fixes (Fast)CGI-based WebDAV and CalDAV (calendar) servers with httpd.

ok benno@ stsp@

Sync with RFC 7230-7235 phrases and IANA registered status codes.

ok reyk@

When opening directories, re-match the location after the index file
has been appended. This allows to use a fastcgi target as the default
index, for example index.php.

OK florian@

branches: 1.5.2;
Allocate http_host instead of carrying a buffer in the descriptor.

It is recommended to use a URL in the Location header of 3xx
responses. To accomplish this, add some semantics to retrieve the
server host name of a connection: either IP, IP:PORT (if not 80) or
[IP6]:PORT, or Host value (if valid).

Sync file to be identical in relayd(8) and httpd(8).

Add support for media types (aka. MIME types): the types section is
compatible to nginx' mime.types file which can be included directly.
If not present, use a few built-in defaults for html, css, txt, jpeg,
gif, png, and js.

Add httpd(8), an attempt to turn the relayd(8) codebase into a simple
web server. It is not finished yet and I just started it today, but
the goal is to provide an HTTP server that a) provides minimal
features, b) serves static files, c) provides FastCGI support, and d)
follows common coding practices of OpenBSD.

It will neither support plugins, nor custom memory allocators, EBCDIC
support, PCRE or any other things that can be found elsewhere.
httpd(8) is not intended to provide a fully-featured replacement for
nginx(8) or the Apache, but it will provide enough functionality that
is needed in the OpenBSD base system.

ok deraadt@

sync http.h with relayd
ok reyk@

Use "compliant" header guards by avoiding the reserved '_' namespace.

Pointed out by Markus Elfring

OK mikeb@ millert@

More http status codes.
OK benno@, reyk@

bump copyright year

SVG is common enough to add it to the default types.

whitespace spotted while studying the code

Add various RFC-based WebDAV methods to the list of accepted HTTP methods.
This fixes (Fast)CGI-based WebDAV and CalDAV (calendar) servers with httpd.

ok benno@ stsp@

Sync with RFC 7230-7235 phrases and IANA registered status codes.

ok reyk@

When opening directories, re-match the location after the index file
has been appended. This allows to use a fastcgi target as the default
index, for example index.php.

OK florian@

branches: 1.5.2;
Allocate http_host instead of carrying a buffer in the descriptor.

It is recommended to use a URL in the Location header of 3xx
responses. To accomplish this, add some semantics to retrieve the
server host name of a connection: either IP, IP:PORT (if not 80) or
[IP6]:PORT, or Host value (if valid).

Sync file to be identical in relayd(8) and httpd(8).

Add support for media types (aka. MIME types): the types section is
compatible to nginx' mime.types file which can be included directly.
If not present, use a few built-in defaults for html, css, txt, jpeg,
gif, png, and js.

Add httpd(8), an attempt to turn the relayd(8) codebase into a simple
web server. It is not finished yet and I just started it today, but
the goal is to provide an HTTP server that a) provides minimal
features, b) serves static files, c) provides FastCGI support, and d)
follows common coding practices of OpenBSD.

It will neither support plugins, nor custom memory allocators, EBCDIC
support, PCRE or any other things that can be found elsewhere.
httpd(8) is not intended to provide a fully-featured replacement for
nginx(8) or the Apache, but it will provide enough functionality that
is needed in the OpenBSD base system.

ok deraadt@