Claire
Claire
That's perplexing. Did you have an issue running the migrations before getting the error you reported in the first post? Can you issue the following SQL query? ```sql REINDEX INDEX...
I'm not sure what's happening there, the migrations says the index exists, but the command you ran says the opposite… did you do anything in-between? What happens if you run...
Maybe revamp those logins with “From this server” and “From another server” instead of “On this server” and “On another server”? I'm not sure how much that would help
Attempting to address that issue in #22490
Some issues were raised privately and somewhat addressed in #19326 by restricting search to exact matches or 5-characters minimum and disallowing pagination
My understanding is that nginx's default behavior should work if the proxied server sets the `Accept-Ranges`, so… does not Rails set it for static files? Does it even support that...
So the issue only occurs when nginx is fetching from cache? I wonder if setting `proxy_force_ranges on` would have adverse effects on non-static content.
Sorry, this past week has been pretty busy. Still trying to wrap my head around the issue. From what I understand: 1. with nginx serving the files directly, byte ranges...
> > `proxy_force_ranges on` would fix the issue with 3, but note that it seems to not actually make nginx cache the file, thus requesting the whole file for each...
This is a duplicate of #10976