-
Notifications
You must be signed in to change notification settings - Fork 82
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Progress endpoint won't respect PrefixPath defined in dashboard UI #125
Comments
The code just uses default Hangfire APIs to register dashboard routes:
I think this might be a bug in Hangfire itself? |
@khellang I saw that you created a fork of this repository, I have a nuget package that extends this one and was thinking about creating 2 additional nugets that target your fork. https://github.com/AnderssonPeter/Hangfire.Console.Extensions |
I'm not totally opposed to it, but the IdentityStream.* prefix is reserved for my company's account on NuGet.org, so I'm not sure how doable it is. Any other suggestions? 😆 |
If that is the case how about |
Yeah, that's fine 👍🏻 |
@khellang seems like anything with the name |
Hmm. That's weird. I wonder what part of "prefix" Microsoft doesn't get? 😆 The prefix is explicitly I'm not too keen on having packages we don't maintain sitting under the IdentityStream NuGet organization either 🤔 |
What about |
It seems that progress circular loading that's shown in overview of running tasks (for each row) doesn't respect PrefixPath defined in dashboard registration. The repeated requests towards
hangfire/console/progress
is never prefixed.As in my case, the dashboard is exposed on sub address (
https://localhost:6001/application/hangfire...
) with PrefixPath defined asapplication
, the progress requests point tohttps://localhost:6001/hangfire/console/progress
The text was updated successfully, but these errors were encountered: