Custom Query (2296 matches)
Results (37 - 39 of 2296)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #2565 | invalid | ویکی | ||
| Description |
Http/vike:domain formatting |
|||
| #2564 | invalid | nginx returns 501 when 400 is expected | ||
| Description |
nginx seems to be exhibiting unexpected behavior when sending an invalid value for the Transfer-Encoding header. I've been using the nginx docker container to test with locally: docker run -p 8080:80 nginx The following curl request results in an HTTP 501: curl -I -X POST -H "Transfer-Encoding: invalid" localhost:8080 According to https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Transfer-Encoding there are only 4 valid values for the Transfer-Encoding header. If a client sends an invalid value, I'd expect the server to respond with an HTTP 400. nginx responds with an HTTP 501. |
|||
| #2563 | duplicate | Does not respect cache-control when using proxy_cache_use_stale updating | ||
| Description |
We have proxy_cache_use_stale updating ... in our proxy configurations, and on some paths, upstream is sending cache-control: no-cache, no-store, must-revalidate pragma: no-cache expires: 0 in a 302 response. It seems that nginx is caching this sometimes, because some clients are receiving 404 and all of those requests are cache_status=UPDATING . It happens for 1 percent of clients and whenever I try to reproduce this I get cache_status=EXPIRED , so I'm not sure how to go further with this. |
|||
