Empresas
Empleos
  • Sobre nosotros
  • Soluciones
    • Publicación de vacantes
      Publica tu vacante y recibe candidatos calificados en 48h.
    • Evaluación de candidatos
      500+ pruebas técnicas y psicológicas, más anti-fraude.
    • Headhunting
      Búsqueda ejecutiva a la medida de principio a fin.
    • Nómina + EOR
      Dispersión de nómina y EOR en más de 15 países de LATAM.
  • Precios
  • Empleos

0

186
Vistas
POST request returns 411 error in Chrome for a small subset of devices

Some POST requests in a small subset of Chrome browsers return 411 error for some reason. The server's endpoint returns 200 in most of the other devices also using Chrome. We're using a load balancer in AWS and our backend is .NET. What could possibly be the reason for this?

Edit: I noticed this only happens when there is no body in the POST request. It could be the browser omitting Content-Length: 0 in the request headers for some reason. But what could be making the browser do such behavior?

over 4 years ago · Santiago Trujillo
1 Respuestas
Responde la pregunta

0

After experiencing the same problem in both Chrome and Edge across two different websites, I think I have the answer:

The problem appears to be BitDefender antivirus.

If I disable BitDefender protection, the post requests succeed.

Bizarrely, if then re-enable BitDefender protection, the issue doesn't come back.

After stumbling across the solution, I found a few references to people having the same problem: https://community.bitdefender.com/en/discussion/88573/status-411-length-required-during-browsing https://support.mozilla.org/en-US/questions/1344632

over 4 years ago · Santiago Trujillo Denunciar
Responde la pregunta
Encuentra empleos remotos

¡Descubre la nueva forma de encontrar empleo!

Top de empleos
Top categorías de empleo
Empresas
Publicar vacante Precios Comercial
Legal
Términos y condiciones Política de privacidad
© 2026 PeakU Inc. All Rights Reserved.
Andres GPT
Recomiéndame algunas ofertas
Necesito ayuda