Alexander Hofbauer
Alexander Hofbauer
@jmsche Ah! Didn't consider there could have been a breaking change in the String component.
Yes, this is fixed.
> What problems did you have? Only my comments on the review. And one of them turned out to be wrong assumptions on my end anyway.
With this simple config: ``` request_header X-Sendfile-Type x-accel-redirect request_header X-Accel-Mapping /private-files= intercept { @accel header X-Accel-Redirect * handle_response @accel { root * /private-files rewrite * {resp.header.X-Accel-Redirect} method * GET header...
Sorry, if this is totally stupid, but is there a way to "segment" the opcache for workers? If an `opcache_reset` is triggered the workers are notified there's a new SHM...
I've seen it after a deployment and attributed it to browser cache, but days afterwards in another project. Come to think of it (caching) again, I think these were two...
After my last comment I've seen the error again and again without any deploys in the meantime.
Not caching the HTML content on the client (i.e., no last modified) "solves" the cache problem. Unfortunately this forces the app to do work for content I know hasn't changed....