9

You know the configuration sucks if it's a one file, 10 K lines nginx reverse proxy configuration.

But what really really really sucks....

If the person who wrote it was a google craptastic copy pasta ninja.

For fucks sake, if you don't know what you are doing, just stop.

I've had this in so many rants, it's terrifying how many devs seem to be completely unaware of what they're doing Oo

This time, fuckwad ignored the basic principle of NGINX configuration: set the HTTP version for the proxy.

It's by default HTTP 1.0 - as HTTP 1.1 requires a Host Header _which you must set if not already present_.

The fuckwad had all kinds of scary optimizations enabled. Literally a bukkaka (not a typo) of <way too high value> and <too obscure configuration value that cannot apply here>.

But the most trivial thing, enabling HTTP 1.1 and keepalive. Nope.

Not in it.

It's funny how fast NGINX can be without the bukkaka of configuration values but HTTP keepalive enabled.

*me sits in the silent corner of the plushy pink room with soft walls*

Comments
  • 1
    @AtuM Yeaaahhh.... Sounds familiar.

    It took a long time to realize named RegEx's group exist in Perl and they are used thoroughly in this fucka.

    (RegExes are not a problem per se, but I'd never thought someone uses named groups and use them as variables over the whole configuration...)

    :( :/ I want my vicodein.
Add Comment