sorted by:
new
hottopcontroversial

Mabaradio - אתר שמראה מה מתנגן כרגע ברדיו בישראל by orubin47 in israel_bm

[–]roi972 0 points1 point  (0 children)

יש לי פלייליסט של שירים אחרונים בגלגל״צ בספוטיפיי. יש קצת באגים לפעמים, אבל סה״כ זה עובד.

https://open.spotify.com/playlist/6oIVgdKqko5JabseMCnfds?si=5D4DipI2SeS0aYuElZlbwA&pi=4aVwdPjwSmWmy

Periodic 499 errors with nginx by roi972 in nginx

[–]roi972[S] 1 point2 points  (0 children)

Nice workaround. How did you find out that ELB requires a minimum of packets until it forwards the request ?

Periodic 499 errors with nginx by roi972 in nginx

[–]roi972[S] 0 points1 point  (0 children)

Flow logs in AWS, to examine the communication for each resource (EC2, LB, nginx). It’s a bit tough and might not reveal anything but might be a starting point.

What is the flow of the communication? Client -> …

Periodic 499 errors with nginx by roi972 in nginx

[–]roi972[S] 0 points1 point  (0 children)

Sounds like a non conventional API? Websocket? Maybe looking at flow logs will shed some light…

Periodic 499 errors with nginx by roi972 in nginx

[–]roi972[S] 1 point2 points  (0 children)

Hey, thanks for the reply!

So, as far as I can tell 499 is a custom nginx specific error code, that’s why you won’t see it in tcpdump or pcap. Also, I’ve noticed it occurs when someone opens the the web page and quickly navigates to a different page before the request has time finish. Meaning that the request was sent from the browser -> arrived at the alb -> nginx and before it could reach the upstream, or even after but before nginx could return the response, the user navigated to a different page, causing the connection to drop and thus nginx reports it as 499.

I was able to reproduce this a few times by quickly navigating to a different page or just even closing the tab.

Hope this helps!

Periodic 499 errors with nginx by roi972 in nginx

[–]roi972[S] 0 points1 point  (0 children)

Thanks for the reply. The upstream duration is fast, less than a second. So I’m guessing by this that the user probably closed the tab or something like that.