Custom Query (2297 matches)
Results (46 - 48 of 2297)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #91 | fixed | when resolver dont works - workers crashes | ||
| Description |
when specified server in resolver directive - does not work all workers which accesses server with proxy_pass http://$host will crash with signal 11 |
|||
| #92 | fixed | The Proxy module doesn't support IPv6 back-ends | ||
| Description |
I've setup Nginx as a reverse proxy for my CDN. However, the proxy-module doesn't use IPv6 at all. Which causes the platform to fail in case of IPv6-only websites or when IPv4 and IPv6 produce different content. Please implement IPv6 in the proxy-backend. Thanks! |
|||
| #98 | fixed | Unable to set Retry-After header with 503 response | ||
| Description |
Currently its not possible to use add_header to set a Retry-After header when responding with a 503 header. This causes a problems when trying to inform clients to retry after a timeout when to bring backends back-up after an error. There are currently work-arounds which involve issuing the headers via a dynamic language (either with a proxy or the perl module) however this may not be possible if these are the cause of the 503. Suggested resolutions: Either allow "add_headers retry-after" for 50x errors, or change the syntax of error_page to allow one to append "retry-after x" to the entry and have nginx add the header. |
|||
