View Issue Details

IDProjectCategoryView StatusLast Update
0004126Rocky ServicesMirror Managerpublic2023-09-07 02:43
ReporterBrian Murrell Assigned ToNeil Hanlon  
PriorityhighSeveritymajorReproducibilityN/A
Status acknowledgedResolutionopen 
Summary0004126: Mirror load-balancer doen't return 503 to client when they incur a 503 trying to fetch content
DescriptionIt would seem that when there is an issue behind the load-balancer trying to fetch content, the load-balancer returns a 200 response to the client, but with HTML content that says:

503 Service Unavailable

No server is available to handle this request.

Here is the log entry from our proxy that indicates that the response was a 200:

2023-09-05T13:33:55.220Z|40ca9f5eefc6c659|rocky-vault-proxy||HEAD|http://dl.rockylinux.org/vault/rocky/8.6/PowerTools/x86_64/os/repodata/145d657619670c3d373c5c3b6ec9e8b51b3386da2980b3dc761b7310a190869a-filelists.xml.gz|200|0|0|10442
2023-09-05T13:34:04.007Z|40ca9f5eefc6c659|rocky-vault-proxy||GET|http://dl.rockylinux.org/vault/rocky/8.6/PowerTools/x86_64/os/repodata/145d657619670c3d373c5c3b6ec9e8b51b3386da2980b3dc761b7310a190869a-filelists.xml.gz|200|0|0|8782

The 200 that is between the |…| in the above log entries is the HTTP status code, but the content that was actually received from the above GET was the:

503 Service Unavailable

No server is available to handle this request.

The problem with all of this is that a client that is going to cache a successful (i.e. 2xx) result is going to cache (and thus serve) erroneous content. If instead the client received the 503 response it would know the fetch was unsuccessful, not cache it and would serve from it's own cache. It would then know to check again for correct content in the near future.
TagsNo tags attached.

Activities

Neil Hanlon

Neil Hanlon

2023-09-07 02:43

administrator   ~0004588

Thank you for the report. I'm looking into this.

Issue History

Date Modified Username Field Change
2023-09-05 15:37 Brian Murrell New Issue
2023-09-07 02:43 Neil Hanlon Assigned To => Neil Hanlon
2023-09-07 02:43 Neil Hanlon Status new => acknowledged
2023-09-07 02:43 Neil Hanlon Note Added: 0004588