Task names with forward slashes cannot be enqueued manually in the web UI

[kevinrobell-st]

Let's say I have two cron tasks one with a forward slash in the name and the other without.

The one with the forward slash returns a 404 when I press the Enqueue Now button and click okay.

The one without the forward slash works as expected without any problems.

This seems like some sort of URL escaping bug at a glance. Not the end of the world though because it can easily be enqueued from the console but it's just something we ran into so I thought I'd mention it.

[markets]

This seems like some sort of URL escaping bug

100% agree, please feel free to send a patch.

Thanks for your detailed report!