Custom Query (2297 matches)
Results (19 - 21 of 2297)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #19 | invalid | Changelog does not list 1.0.6 changes | ||
| Description |
http://nginx.org/en/CHANGES does not have an entry for the current (stable) release - 1.0.6 |
|||
| #20 | invalid | error_page directive inconsistently applied | ||
| Description |
server {
server_name sub.domain.tld;
root /home/user/sub.domain.tld;
error_page 414 /414_request_uri_too_long.html;
}
Make a request for a very long URI, with over 8K characters: http://sub.domain.tld//testing_414_request_uri_too_long_testing_414_request_uri_too_long_ ... testing_414_request_uri_too_long Expect to have contents of /414_request_uri_too_long.html delivered with a 414 HTTP status code. Instead, <html> <head><title>414 Request-URI Too Large</title></head> <body bgcolor="white"> <center><h1>414 Request-URI Too Large</h1></center> <hr><center>nginx</center> </body> </html> is returned with a 200 status code. |
|||
| #21 | fixed | Incorrectly caching pages with non-cacheable Cache-Control headers | ||
| Description |
When
Is set. When a shift reload is performed we set the object as cacheable after we have checked for the privacy headers. So we cache it when we shouldn't. Possible patch attached |
|||
