---
title: "Discussion on \"We Debugged \"Random\" 502 Errors for 2 Days. The Answer Was in One HTTP Header Nobody Looked At\" | Hashnode"
description: "Discussion on \"We Debugged \"Random\" 502 Errors for 2 Days. The Answer Was in One HTTP Header Nobody Looked At\". The 502s hit about one login in fifty, and they looked completely random, which is the worst possible bug. Our application logs showed a clean 200 for every one of those requests. Our monitoring showe"
url: "https://hashnode.com/posts/we-debugged-random-502-errors-for-2-days-the-answer-was-in-one-http-header-nobody-looked-at/6af5c5cd5c12b5ed95960268"
---

[Feed](https://hashnode.com/feed) /

Discussion

# [We Debugged "Random" 502 Errors for 2 Days. The Answer Was in One HTTP Header Nobody Looked At](https://pureengine.hashnode.dev/we-debugged-random-502-errors-for-2-days-the-answer-was-in-one-http-header-nobody-looked-at?utm_source=hashnode&utm_medium=feed)

The 502s hit about one login in fifty, and they looked completely random, which is the worst possible bug. Our application logs showed a clean 200 for every one of those requests. Our monitoring showe

5d ago · 4 min read · pureengine.hashnode.dev  
Read the article

## Written by

[kamen](https://hashnode.com/@kamen-ivanov)

@kamen-ivanov · Varna, Bulgaria

  
[View profile](https://hashnode.com/@kamen-ivanov)

Team Lead and Senior Backend Engineer with 11+ years building Java and Spring Boot systems. I write about architecture that survives changing requirements, teams, and technologies - through a Git-tagged reference microservice and production lessons from Java, Hibernate, Kafka, Redis, and SQL systems.

## Responses

Markdown supported · ⌘↵ to post

No responses yet.
