Lines Matching refs:response
138 *) Bugfix: the "return" directive did not change the response code when
238 *) Bugfix: it was possible to specify an incorrect response code in the
266 when returning a large response.
285 "subrequest_output_buffer_size" directive defines maximum response
346 *) Bugfix: some parts of a response might be buffered when using
362 backend returned a "101 Switching Protocols" response to a
399 *) Bugfix: when using HTTP/2 nginx might return the 400 response without
424 *) Bugfix: incorrect response length was returned on 32-bit platforms
428 "If-Range" request header line did not use the response last
529 address, the source address of a response UDP datagram could differ
594 extensions in the "Cache-Control" backend response header line.
638 *) Bugfix: an incorrect response might be returned when using the
642 *) Bugfix: a truncated response might be stored in cache when using the
738 *) Bugfix: nginx did not write anything to log and returned a response
778 *) Bugfix: nginx returned the 400 response on requests with the "-"
808 *) Bugfix: an incorrect response might be returned when using the "aio
905 *) Change: the "421 Misdirected Request" response now used when
928 *) Workaround: a response might not be shown by some browsers if HTTP/2
1003 *) Feature: Huffman encoding of response headers in HTTP/2.
1046 response processing if the "resolver" directive was used, allowing an
1050 *) Security: use-after-free condition might occur during CNAME response
1152 response from cache.
1249 *) Bugfix: OCSP stapling might return an expired OCSP response in some
1424 advance that the response will not be cached (e.g., when using
1432 response will be made.
1453 backend response header line.
1475 backend response while caching.
1487 *) Bugfix: the last part of a response received from a backend with
1574 returned a malformed response; the bug had appeared in 1.5.8.
1600 *) Feature: weak entity tags are now preserved on response
1609 was no Last-Modified header in a response returned from cache.
1871 "Cache-Control" response header line with an empty value.
1982 *) Change: now after receiving an incomplete response from a backend
1983 server nginx tries to send an available part of the response to a
2230 *) Bugfix: a "100 Continue" response was issued with "413 Request Entity
2243 *) Bugfix: proxied HEAD requests might return incorrect response if the
2453 backend returned incorrect response.
2481 *) Bugfix: response might be truncated if there were more than IOV_MAX
2538 client if backend returned specially crafted response.
2765 request was proxied and response status code was 206.
2785 resolver got a big DNS response.
2797 "Content-Length" response header line if the "start" argument was
2916 response size, then nginx disables ranges and returns just the source
2917 response.
3063 *) Bugfix: a cached response may be broken if "proxy/fastcgi/scgi/
3345 response saving only.
3360 *) Bugfix: SSI response might be truncated after include with
3422 "Refresh" response header line.
3484 "Cache-Control" backend response header line.
3487 used, if empty response has 200 status code.
3549 was large stderr output before FastCGI response; the bug had appeared
3561 stderr output before response.
3627 negative number was set in the "Cache-Control" response header line.
3644 *) Bugfix: nginx closed a connection if a cached response had an empty
3655 *) Bugfix: nginx cached a 304 response if there was the "If-None-Match"
3751 *) Bugfix: nginx always added "Content-Encoding: gzip" response header
3842 "Cache-Control" backend response header line.
3848 *) Bugfix: the "Set-Cookie" and "P3P" FastCGI response header lines were
3881 *) Bugfix: nginx sent '\0' in a "Location" response header line on MKCOL
3922 *) Bugfix: nginx always added "Vary: Accept-Encoding" response header
3954 *) Bugfix: an expired cached response might stick in the "UPDATING"
4048 response header.
4052 response header lines; the bug had appeared in 0.7.44.
4056 empty response; the bug had appeared in 0.8.5.
4108 "WWW-Authenticate" response header line.
4130 *) Bugfix: the "Set-Cookie" and "P3P" response header lines were not
4322 *) Feature: the "try_files" directive supports a response code in the
4325 *) Feature: now any response code can be used in the "return" directive.
4351 "Expires", and "Cache-Control" header lines in a backend response.
4410 "Last-Modified" response header line; the bug had appeared in 0.7.44.
4501 *) Bugfix: large response with SSI might hang, if gzipping was enabled;
4573 *) Bugfix: a double response might be returned if the epoll or rtsig
4610 line as response body instead of default 404 page body; the bug had
4633 *) Bugfix: a "100 Continue" response was issued for HTTP/1.0 requests;
4696 *) Bugfix: nginx did not process a FastCGI server response, if the
4697 server send too many messages to stderr before response.
4866 *) Bugfix: a full response was returned for request method HEAD while
5094 *) Bugfix: nginx did not process FastCGI response if header was at the
5160 *) Bugfix: if response code 495-497 was redirected via an "error_page"
5192 check a response length.
5333 kqueue, then nginx issued an alert "name is out of response".
5342 server, then nginx returned usual response.
5370 "Last-Modified" response header line.
5394 returned response in HTTP/0.9 version.
5425 *) Bugfix: nginx returned the 400 response on requests like
5499 did not hide response header lines whose name was longer than 32
5509 *) Bugfix: if backend returned response header only using non-buffered
5590 "Last-Modified" response header line.
5592 *) Bugfix: if a response different than 200 was returned to a request
5732 *) Bugfix: a part of response body might be passed uncompressed if gzip
5786 *) Bugfix: trailing boundary of multipart range response was transferred
5947 *) Bugfix: the response was incorrect if several ranges were requested;
5954 *) Bugfix: the "0" response code might be logged in the access_log
6027 header line in response.
6130 "0.000", although response time was more than 1 millisecond.
6150 IMAP/POP3 proxy authentication server response.
6192 "add_after_body" directive, then a response did not transferred
6207 *) Bugfix: the 50th subrequest in SSI response did not work; the bug had
6215 *) Bugfix: if a big static file was included using SSI in a response,
6216 then the response may be transferred incomplete.
6237 while waiting authentication server response the IMAP/POP3 proxy
6295 *) Bugfix: nginx sent the chunked response for HTTP/1.1 request,
6320 response code redirected by the "error_page" directive.
6425 response when the "X-Accel-Redirect" was used.
6497 *) Bugfix: if a response of proxied server or FastCGI server was
6542 *) Bugfix: if a code response of the PUT request was 409, then a
6561 *) Feature: the "X-Accel-Charset" response header line is supported in
6570 *) Bugfix: if the "Content-Length: 0" header line was in response, then
6586 response has no "Content-Type" header line.
6617 *) Feature: the "X-Accel-Buffering" response header line is supported in
6673 "Cache-Control" response header line.
6856 many warnings before the response.
6861 *) Bugfix: nginx returned the 502 response, if the complete response
6886 *) Bugfix: the proxied response body generated by the "post_action"
6934 *) Bugfix: now a response generated by the "post_action" directive is
7080 *) Bugfix: in the 304 response the body was transferred; the bug had
7174 chunked response was encoded incorrectly.
7232 *) Bugfix: if the response was ended just after the SSI command and
7233 gzipping was used, then the response did not transferred complete or
7302 after the response header was transferred to a client.
7541 directive was canceled; the "charset" directive sets the response
7545 transferred while the 401 response code redirecting.
7556 *) Bugfix: if the backend response had the "Location" header line and
7557 nginx should not rewrite this line, then the 500 code response body
7579 *) Feature: the "X-Accel-Limit-Rate" response header line is supported
7586 *) Bugfix: the response status code was not changed when request was
7595 *) Bugfix: nginx treated the backend response as invalid if the status
7616 *) Bugfix: if all backends had returned the 404 response and the
7650 *) Bugfix: the segmentation fault was occurred if the backend response
7657 *) Bugfix: the segmentation fault might occur if the response was bigger
7660 *) Bugfix: nginx returned the 400 response on requests like
7668 big response part were include by SSI.
7704 *) Feature: the "X-Accel-Redirect" response header line is supported in
7710 *) Bugfix: the response encrypted by SSL may not transferred complete.
7712 *) Bugfix: errors while processing FastCGI response by SSI.
7717 response body; the bug had appeared in 0.1.30.
7725 *) Bugfix: the response encrypted by SSL may not transferred complete.
7727 *) Bugfix: if the length of the response part received at once from
7729 500 response code; in proxy mode the bug had appeared in 0.1.29 only.
7734 *) Feature: the "return" directive can return the 204 response code.
7801 headers or a backend response header.
7803 *) Bugfix: if the backend did not transfer response for a long time and
7805 returned the 408 response.
7808 invalid line in response header; the bug had appeared in 0.1.26.
7904 response for existent directory, if this directory was used in
7934 the response header if the no response was transferred to a client.
8036 *) Bugfix: if the response were transferred by chunks, then on the HEAD
8045 *) Bugfix: the compressed response encrypted by SSL may not transferred
8053 *) Bugfix: the response code 400 was returned for the POST request with
8148 transferred response.
8163 an error while the response waiting then process may got caught in an
8286 *) Bugfix: with sendfile the response was not recoded according to the