Xhr search requests return 406

Installation
6

Meta runs behind an AWS ALB reverse proxy and doesn’t exhibit this problem.

Try runs behind an HAProxy reverse proxy and doesn’t exhibit this problem.

Most self hosted instances only have the internal nginx reverse proxy and also doesn’t exhibit this problem.

That makes me suspect the Azure Front Door. This won’t be the first time an Azure product has weird broken behavior.

We also have experience with other WAF products breaking Discourse, so they aren’t supported.

1 Like