Error: upstream sent too big header while reading response header from upstream

[slashrsm]

This happens in development environment when

parameters:
  http.response.debug_cacheability_headers: true

is enabled. I suspect that cacheability debug header becomes quite big on a bit complex sites and hits the default limits in nginx.

I Googled a bit and found a solution that increases limits:

fastcgi_buffers 16 16k;
fastcgi_buffer_size 32k;

I am not sure if we want to include this in the default config and we also do not have dev flavor of the image. I am also not sure how this affects performance. I suspect that it causes each request to consume a bit more memory, which could mean that you would be able to serve less concurrent requests given the same amount of memory.

Anyone else experienced this? Thoughts?

[Calystod]

I confirm the bug.

[Calystod]

I try to replace the drupal.conf by a modify version but I have the error

sed: can't move '/etc/nginx/conf.d/drupal.confNBahKG' to '/etc/nginx/conf.d/drupal.conf': Resource busy

I copy the image and modify the drupal.conf file. It works correctly.

[Calystod]

I do a pull request #25
Seems another exist and fix the same thing #22