-
Notifications
You must be signed in to change notification settings - Fork 867
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
Application redirects to /active when used as express middleware #592
Comments
whats your kue version? |
8.1.2 |
we have no 8.1.2 version, dya mean 0.8.12 ? |
if so, 0.8.12 is based on express 3.x and I don't think it can sit as a middleware in an express 4 app |
however I'm not an express man, so any patches are welcome if anybody can provide something to fix this |
Ups sorry :) yes is 0.8.12. I had a look at the code but is really simple, so the problem could be a little weird. Hope to have time to look into this a bit more in the next weeks |
have you tested if the above code (express 4.x) works in kue 0.9.0 ? |
I'm experimenting the same trouble. I'll take a look to the code |
Seems like this is related to the Express version. In my case using 3.x, where the |
I've created a PR that should fix this issue. #594 |
fix(#592): bad redirect URL in old express versions
tested in 0.9.0, thank you @h2non |
I need to secure Other endpoints are authenticated by other methods. I am trying as follows: var basicAuth = require('basic-auth-connect')
....
// Securing dashboard app
var subApp = express()
// add authentication
subApp.use(basicAuth('foo', 'bar'))
// re-add kue.app (but dont put it in its own folder)
subApp.use('', messagesMod.kueDashboardApp)
server.use('/kue', subApp) |
If I call I am using |
why not to use |
As reported by @digitaljohn and me in #587.
Step to reproduce:
use kue app in a express application:
try to reach http://localhost:3000
Expected behaviour:
Redirect to http://localhost:3000/active
Actual behaviour:
Redirected to http:///active/
Kue version: 8.1.2
Express version: 3.1.2
Npm version: 2.7.4
Node version: 0.12.2
The text was updated successfully, but these errors were encountered: