Static cache bug #1

New Issue

Closed

opened 2022-07-19 07:51:11 -05:00 by rudism · 1 comment

rudism commented

2022-07-19 07:51:11 -05:00

Owner

Seems the server starts serving 0 byte responses for static files at some point (even though the Content-Length header has the correct response size). Clearing the data/cache directory fixes it, leading me to believe it's a problem with the static file cache stuff.

I haven't observed the same problem with plan responses through the API, only static files.

Seems the server starts serving 0 byte responses for static files at some point (even though the `Content-Length` header has the correct response size). Clearing the `data/cache` directory fixes it, leading me to believe it's a problem with the static file cache stuff. I haven't observed the same problem with plan responses through the API, only static files.

rudism added the

bug

label 2022-07-19 07:51:11 -05:00

rudism commented

2022-07-19 09:52:05 -05:00

Author

Owner

I think this is because my uptime monitor is making HEAD requests and the server is caching those responses (which will contain the content length but no actual content). Need to ensure cache is only written on GET requests.

I think this is because my uptime monitor is making `HEAD` requests and the server is caching those responses (which will contain the content length but no actual content). Need to ensure cache is only written on `GET` requests.

rudism referenced this issue from a commit

2022-07-19 09:56:00 -05:00

only caching GET requests for static files

rudism closed this issue

2022-07-19 09:56:00 -05:00

This repo is archived. You cannot comment on issues.