me@jackbenda.com 13 Posted 7 hours ago Posted 7 hours ago Sorry, should've been clearer. I'm not hitting this myself; I've stayed on 4.9.5.0 specifically because of this thread. Just trying to work out from others' experience whether it's worth updating and living with the regression short-term, or holding off until there's a fix. Nothing to try on my end yet since I haven't upgraded. 1
Cr8iveLosr 103 Posted 2 hours ago Author Posted 2 hours ago 4 hours ago, me@jackbenda.com said: Sorry, should've been clearer. I'm not hitting this myself; I've stayed on 4.9.5.0 specifically because of this thread. Just trying to work out from others' experience whether it's worth updating and living with the regression short-term, or holding off until there's a fix. Nothing to try on my end yet since I haven't upgraded. TBH, I don't think there's much reason to hold off on the update at this point. It's been about a week, and there haven't been widespread reports of this issue. Did something change between 4.9 and 4.10? Yes. Luke's acknowledged that 4.10 is using an updated .NET 8 maintenance version and that it's possible a security-related change is now preventing something that previously worked. My setup and situation could just be unique enough that it happened to catch a change from behavior that was previously more lax to something that's now being enforced more implicitly. Another person running into the same thing and providing logs would definitely be beneficial in narrowing that down. That said, if you do update and run into the issue, downgrading is pretty easy and gets things working again. Good luck.
Luke 43129 Posted 37 minutes ago Posted 37 minutes ago It seems solvable via nginx configuration, at least according to what I've read.
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now