You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
When launching a site with uSync installed, and InstallUnattended configured, uSync sometimes returns a page "uSync all the things | You are seeing this page because your site doesn't contain any published content". The page's Http status code is 200. As the page is effectively saying "there's no content here", the page should return 404.
When uSync isn't installed, but Umbraco is launched with InstallUnattended set to true, the default "no content yet" type page returns 400.
I'm trying to use the HTTP status code of a server as an automated check to see if a staging server is ready to promote automatically to production. When using a non-uSync installation, I can check curl --fail http://localhost:80/ || exit 1, and when Umbraco returns 2xx, I can be satisfied that the site is ready to promote to production. In a uSync configured site 2xx is returned, even when a content import failed, so I need to do additional checks.
Describe the solution you'd like
uSync's status code should match the default Umbraco 400 or 500 status code. Ideally the "uSync all the things" page would be a 404, since it indicates no content was found at the address.
Describe alternatives you've considered
My current work-around is to check the HTML content of the homepage for some predictable string. It's not a great long-term solution to the issue though.
Additional context
See screenshot of the 2xx status
The text was updated successfully, but these errors were encountered:
what version of Umbraco do you have., for both v10 (v10.8.3) v13 (v13.0.3) a fresh install of Umbraco (no content no packages) the default no-nodes page return 200 🤔 .
v10.8.3
v13.0.3
I don't mind making uSync return a 404, but if it's not the default behavior, i am worried it might affect other people the opposite way.
Looks like I've mis-reported this. The 500 is returned when InstallUnattended is set to false. I might raise a discussion in the Umbraco-CMS repo instead to see if they'd be up for returning 4xx on the InstallUnattended-but-no-content page.
As part of a clean-up effort to better manage our backlog, we are closing older issues especially related to older versions.
Since we last looked at this issue, we've made significant changes and improvements in newer versions, hopefully this is something that is no longer relevant 🤞.
we are closing this because as of now, we mimic Umbraco's standard response codes, and it doesn't look like they are changing them, (sepeically for v13 branches) we will keep an eye on it as new releases come out.
Is your feature request related to a problem? Please describe.
When launching a site with uSync installed, and InstallUnattended configured, uSync sometimes returns a page "uSync all the things | You are seeing this page because your site doesn't contain any published content". The page's Http status code is 200. As the page is effectively saying "there's no content here", the page should return 404.
When uSync isn't installed, but Umbraco is launched with
InstallUnattended
set to true, the default "no content yet" type page returns 400.I'm trying to use the HTTP status code of a server as an automated check to see if a staging server is ready to promote automatically to production. When using a non-uSync installation, I can check
curl --fail http://localhost:80/ || exit 1
, and when Umbraco returns 2xx, I can be satisfied that the site is ready to promote to production. In a uSync configured site 2xx is returned, even when a content import failed, so I need to do additional checks.Describe the solution you'd like
uSync's status code should match the default Umbraco 400 or 500 status code. Ideally the "uSync all the things" page would be a 404, since it indicates no content was found at the address.
Describe alternatives you've considered
My current work-around is to check the HTML content of the homepage for some predictable string. It's not a great long-term solution to the issue though.
Additional context
See screenshot of the 2xx status
The text was updated successfully, but these errors were encountered: