Too big headers on nginx problem

  • Wace

    (@wace)


    3 years, 4 months ago

    Hello,

    While migrating on of the wp sites with query monitor enabled, I’ve run into problem with nginx + php-fpm config, some pages crashing (mostly ajax call), and the only detectable message was upstream sent too big header in the logs. Took me hours to figure out, and it seems to me that the problem was caused by your plugin.

    The only difference between two machines was php version, so query monitor was literally flooded with ‘deprecated’ errors, and I suspect they were causing headers to inflate.

    I’m not the one who was installing/using the plugin, and I don’t have much experience with it, so, unless it’s already taken care of, I would recommend several modifications to the plugin code:

    • disable “deprecated” errors by default;
    • set some kind of header size limit check with possible warning to the user when it’s over one.

    Trying to be helpful, no offense & thank you for your work.

Viewing 1 replies (of 1 total)
  • Plugin Author John Blackbourn

    (@johnbillion)

    WordPress Core Developer

    3 years, 4 months ago

    Yeah this has been reported a few times, most recently here: https://github.com/johnbillion/query-monitor/issues/708 . The problem with hiding errors or limiting the number of errors is that does unfortunately mean errors can get missed if they only get triggered during an Ajax call.

    I think I will need to introduce a limit to the number of errors though, as it’s quite easy to exceed the default 4KB header size limit in Nginx.

Viewing 1 replies (of 1 total)

The topic ‘Too big headers on nginx problem’ is closed to new replies.