417 error makes backoffice unusable

[Ric-Carey]

Which Umbraco version are you using? (Please write the exact version, example: 10.1.0)

10.8.8 (also recreated in 13.5.2)

Bug summary

Hi,

Client in 10.8.8 Umbraco has reported instances of the CMS being unresponsive – Umbraco Forms not loading, Nodes not loading, slide out dialog windows being blank - but only intermittently.

I’m not 100% sure if this is the same issue but I have managed to recreate their symptoms with a strange bug. I have also recreated the same thing in a completely separate 13.5.2 website so appears to be a wider underlying Umbraco issue.

The original website is still rendering Umbraco Forms via the Rich Text Editor Macro method (old school). This is where I have noticed the issue:

If you add a macro with an Umbraco form in to the rich text editor – using the default, Umbraco Forms with Theme macro, Choose a form, choose a theme. Confirm. Save and publish. This will work fine. If you then go back into Umbraco. Click the macro area, click the macro button – the slide out panel will show the data fine. If you then click the Info content tab, click the URL of the page (which opens in a new tab) then go back to the rich text editor, click the macro and then the macro button – the slide out panel will slide out but will be blank. In the Browser console there is a 417 error message connected with the Angular XHR post request. But it gives no real further information other than

{"Type":null,"Title":null,"Status":417,"Detail":null,"Instance":null,"Extensions":{"traceId":"00-2153124195a26cf682c328ae96f39462-6835e97d8973e14c-00"}}

There is no entry in the log corresponding with this.

However, (and this is the key issue) if you were to recreate the error above, once the 417 request happens, the backoffice will now no longer load anything further – with all requests returning 417. E.g. if you close the slide out panel, and try and navigate to another node (clicking discard changes) – it will not load just showing the blue loading dots. If you click into another section, the section will change the tree will load but it wont load any inner details e.g. the log etc, if you click into forms section, the forms show in the tree but wont load returning the red notification banners.
If you then refresh the browser – it all returns to life as normal.

Obviously, the steps to recreate are very specific, but I am conscious that perhaps there is another way to trigger this underlying 417 error which is what the client has done in day to day editing – and Umbraco has just stopped working for them (unbeknown they just need to refresh the browser). I’m conscious there is something underlying internal which is the root cause. If it runs into an error it shouldn’t just completely stop working if its been caught? I have been able to recreate in a separate website (13.5.2) using the same method.

Please let me know if you need more information?

Many thanks,
Ric

Specifics

No response

Steps to reproduce

f you add a macro with an Umbraco form in to the rich text editor – using the default, Umbraco Forms with Theme macro, Choose a form, choose a theme. Confirm. Save and publish. This will work fine. If you then go back into Umbraco. Click the macro area, click the macro button – the slide out panel will show the data fine. If you then click the Info content tab, click the URL of the page (which opens in a new tab) then go back to the rich text editor, click the macro and then the macro button – the slide out panel will slide out but will be blank. In the Browser console there is a 417 error message connected with the Angular XHR post request. But it gives no real further information other than

Expected result / actual result

No response

[github-actions]

Hi there @Ric-Carey!

Firstly, a big thank you for raising this issue. Every piece of feedback we receive helps us to make Umbraco better.

We really appreciate your patience while we wait for our team to have a look at this but we wanted to let you know that we see this and share with you the plan for what comes next.

• We'll assess whether this issue relates to something that has already been fixed in a later version of the release that it has been raised for.
• If it's a bug, is it related to a release that we are actively supporting or is it related to a release that's in the end-of-life or security-only phase?
• We'll replicate the issue to ensure that the problem is as described.
• We'll decide whether the behavior is an issue or if the behavior is intended.

We wish we could work with everyone directly and assess your issue immediately but we're in the fortunate position of having lots of contributions to work with and only a few humans who are able to do it. We are making progress though and in the meantime, we will keep you in the loop and let you know when we have any questions.

Thanks, from your friendly Umbraco GitHub bot 🤖 🙂

[NguyenThuyLan]

Hi @Ric-Carey , I believe that I followed your steps to reproduce but couldn't get the error like you did, could you look at my video below?

Content.-.localhost.-.Google.Chrome.2025-02-20.14-27-56.mp4