This blog is updated daily.
A general description is here.
‘as(object, name)’ signalled an error when ‘class(object)[1]’ was not formally defined and ‘class(object)[-1]’ contained ‘name’, never searching for a method for ‘coerce’ with signature ‘c(from="ANY", to=name)’. Now it searches and signals an error only on failure. Thanks to Michael Chirico for the report (PR#19023).
The internal HTTP server (used by the dynamic help system) removes dot segments (‘/../’ and ‘/./’) also when they were percent-encoded and on Windows converts ‘\’ to the ‘/’ path separator. Paths that include ‘%00’ are rejected.
The internal HTTP server accepts request and header lines of up to 16k bytes (previously 1k) so that requests with many cookies no longer fail. This matters since browsers also send cookies set by any other web application running on ‘localhost’, as cookies are not specific to a port.
The internal HTTP server no longer decodes ‘+’ as a space in the request path (only in the query string) and no longer removes dot segments from the query string.
The internal HTTP server now handles line endings split across network packets, responds with an error instead of waiting when a request or header line is too long, no longer corrupts request headers over 1k bytes in total and drops requests that were closed by the client before they were complete.
The internal HTTP server now sends 1xx, 204 and 304 responses without a body (as required by RFC 9110), skips empty response headers and responds with an error when a handler returns an invalid status code.
The internal HTTP server now rejects requests with ambiguous framing (as required by RFC 9112): ‘Transfer-Encoding’ (not supported), invalid or conflicting ‘Content-Length’, whitespace before the colon in a header field and more than one ‘Host’ header. Previously such requests could be misread.
