U4-2059 - Ping keep alive service doesn't work

Created by Shannon Deminick 05 Apr 2013, 17:18:21 Updated by Shannon Deminick 08 Dec 2014, 04:01:42

Relates to: U4-5391

Relates to: U4-5965

Currently in the keep alive service we have this code:


the "umbracoUrl" is actually never set in the Application collection but also the sender will never be the correct sender either since this happens in a non-web based thread. no idea how this used to work.

We'll need to change some code so that we store the first original URL in our ApplicationContext. this all stopped working in 4.10 with the new UmbracoModule because we were not setting "umbracoUrl" in the application items.


Stefan Kip 07 Nov 2014, 13:51:08

We're experiencing an issue with "storing the first original URL", because that will probably be the public facing URL (www.example.org), while we return '404 Not Found' when someone requests '/umbraco/*' from the public facing website. So for example 'http://www.example.org/umbraco/RestServices/ScheduledPublish/Index' will return a 404 Not Found, which breaks the ScheduledPublishing... Maybe there should be the ability to overrule this first URL with a URL configured in the AppSettings?

Shannon Deminick 11 Nov 2014, 04:37:21

Yup, that's listed here: http://issues.umbraco.org/issue/U4-5391

Stefan Kip 11 Nov 2014, 07:50:47

Thanks Shannon, voted :-)

Priority: Normal

Type: Bug

State: Fixed

Assignee: Shannon Deminick

Difficulty: Normal


Backwards Compatible: True

Fix Submitted:

Affected versions: 4.10.0, 4.11.0, 6.0.0, 4.11.1, 4.11.2, 4.11.3, 4.11.4, 6.0.1, 4.11.5, 6.0.2, 4.11.6, 6.0.3

Due in version: 6.0.4, 4.11.7


Story Points: