Assets failing to load randomly with 502

[ChasNelson1990]

In my chrome browser for [wrc-stg.fjelltopp.org|http://wrc-stg.fjelltopp.org] I keep get assets (vendor.js, fileinputcomponent.js, fontawesome, css etc…) randomly failing to load with 502s….

• It’s really common (something failing to load on a majority of page refreshes)
• It’s typically something failing different on each refresh
• Nginx logs saying there’s {{no valid HTTP/1.0 header while reading response header from upstream}} CKAN logs seem to be showing a 404 not found for these requests.
• But on a hard refresh (shift f5) nothing ever seems to fail…

My best idea… The last point is particularly interesting? Maybe the webassets are changing their names and a hard refresh is pulling a new html document which is requesting the new asset names, but when using the cached html document the browser is requesting assets old assets no longer available for some reason.

[ChasNelson1990]

Some updates from me trying to recreate:

• On Linux and Chromium and using the prod site I am getting one 502 roughly every 10 soft refreshes; much lower than reported above - it seems only to be xxxxxx_main.js

• The message in the nginx logs is confirmed

• I am a bit confused about the comment about the CKAN logs - the 404 isn’t obviously linked for me; the xxxxxx_main.js file is actually returned with a 304 (i.e. it should use the client-side cached version anyway)

• I have gone in and checked the compiled webasset files in the pod and the xxxxxx_main.js was last modified on 2024-09-05 so I don’t think it’s Jonathan reenaming idea Originally posted by ChasNelson1990 on Jira.

[ChasNelson1990]

Just tested on local and assets always loaded (the machine I used is fairly slow, so shouldn’t be caused by just the speed of the server) Originally posted by mixmixmix on Jira.