U4-9772 - ScheduledPublishing fails silently when site is running over HTTPS and umbracoUseSSL is "false"

Created by Jason Elkin 13 Apr 2017, 15:35:47 Updated by a david 04 Sep 2018, 16:19:09

Steps to replicate:

1. Set <add key="umbracoUseSSL" value="false" /> in web.config
2. Run site at {{https://example.com}} and redirect {{http://example.com/(.*)}} to {{https://example.com}}
3. Schedule content to publish or un-publish.

Nothing happens, but logs show the following (filtered) without any error:

DEBUG - [ScheduledTasks] Task added Umbraco.Web.Scheduling.ScheduledTasks
DEBUG - Scheduled publishing executing @ http://www.example.com/umbraco/RestServices/ScheduledPublish/Index
DEBUG - Begin request: https://www.example.com/umbraco/RestServices/ScheduledPublish/Index.
DEBUG - Scheduled publishing complete (took 69ms)
DEBUG - [ScheduledPublishing] Task added Umbraco.Web.Scheduling.ScheduledPublishing

As soon as we set in the Web.Config file in production then everything works fine, but note the subtle change in the logs:

DEBUG - Scheduled publishing executing @ https://www.example.com:443/umbraco/RestServices/ScheduledPublish/Index
DEBUG - Begin request: https://www.example.com/umbraco/RestServices/ScheduledPublish/Index.{code}

I appreciate that the initial configuration is technically wrong, but I'd expect some kind of error message.

EDIT: When I looked in Application Insights and I've discovered that all calls to the URL https://www.example.com/umbraco/RestServices/ScheduledPublish/Index were resulting in a 500 error.

I can only see this because AI logs all HTTP requests and their status code. No exceptions were raised that made it to Umbraco the logs.

I can only guess that Umbraco was just happy that it got a response, and logged the scheduled task as having been completed, ignoring the fact the the URL ultimately returned a 500 status.

Now that I have set the HTTP requests no longer result in an 500 error.

Comments