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
Web Interface Doesn't work properly (redirects to /active without hostname) #715
Comments
which kue version @TylerBrock ? |
0.9.5
|
I have the same problem, but when using kue ui there is no problem & both UIs works fine. |
This should be caused by the latest commits to support for embedding kue inside other express apps. please check 447f525 |
That fixes it but for the simple use case I outline above (the hostname is now included) but it still doesn't respect the outer context with regards to where it's mounted. For example I'm mounting the application at "/queue" but visiting |
It seems I can work around it by specifying a path when mounting kue in the sub-app by specifying Thanks for maintaining this btw. Great stuff. |
Any one can provide a more general PR to handle all scenarios? |
Hi, |
does this work for both express 3 and express 4 !? |
I've tried with express 4 only, let me recheck with express 3 as well. |
Redirection from subfolder is failing. on express 3 |
I believe all two cases for both express versions (4 scenarios) should be considered to be fixed. |
This fix tested both on express v3 and v4, redirection on root and subfolder is working now. Please review. |
nice @azimgd |
I had some troubles with running kue-ui itself, but setting it up as described in documentation and accessing kue interface via /api produces correct redirections.
|
i will test and merge this in a few days @azimgd |
Any updates on this @behrad ? |
tested and merged |
Could you please publish a new version including this fix? Thanks. |
Done! |
Hey everyone, I've tried starting the web interface as described in the documentation:
When the app runs and I visit "http://localhost:3000" in a browser it redirects to "/active" without the scheme and hostname portion of the URL. Manually entering back the scheme and hostname allows the /active page to render but without any assets or javascript.
I've tried loading the page in Chrome 45 and Safari (latest version) with the same result.
The text was updated successfully, but these errors were encountered: