Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

False positive version mismatch behind load balancer #712

Open
adamthehutt opened this issue Feb 7, 2025 · 0 comments
Open

False positive version mismatch behind load balancer #712

adamthehutt opened this issue Feb 7, 2025 · 0 comments

Comments

@adamthehutt
Copy link

adamthehutt commented Feb 7, 2025

We're using Inertia (via Nova) behind a load balancer.

Each server builds its own assets. The compilations and hashes are deterministic, but the files are sometimes listed in a different order in the manifest.json file from one server to the next. Because Inertia uses an md5 hash of the manifest.json file as for its version check, this results in frequent false positive version mismatches.

Would it be possible to use something less error-prone for the versioning check? The most error-proof option would be to parse and sort the json, but that could add excess overhead to each request. Is there a way to access the hash of the last git commit?

As is, Nova is almost unusable for us because of all the full page reloads when Inertia responds to a request with a 409 error.

# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant