Las solicitudes de búsqueda Xhr devuelven 406

[Falco]

Meta se ejecuta detrás de un proxy inverso AWS ALB y no presenta este problema.

Try se ejecuta detrás de un proxy inverso HAProxy y no presenta este problema.

La mayoría de las instancias autohospedadas solo tienen el proxy inverso nginx interno y tampoco presentan este problema.

Esto me lleva a sospechar de Azure Front Door. No será la primera vez que un producto de Azure tenga comportamiento extraño y defectuoso.

También tenemos experiencia con otros productos WAF que rompen Discourse, por lo que no son compatibles.

Discourse + Web Application Firewall (WAF) mod_security

This is a bad idea and it is not recommended. The benefit of this type of thing for a JavaScript app is extremely limited and it adds significant complexity to your hosting setup.

Discourse + Web Application Firewall (WAF) mod_security

I think the desire for some magic device that auto mitigates issues is somewhat misguided in the Discourse setup. We have a bounty program, we patch issues in Discourse within hours of when they are reported. Sites run tests-passed by default which in today’s case contains commits from today. Sure if you are running software that was exploited years ago and you have no freedom to upgrade cause … reasons… a WAF makes sense cause it could save you. But in the case of Discourse I think it is at be…