-
Notifications
You must be signed in to change notification settings - Fork 1.2k
various fixes for getting Nginx auth_request mode working #319
Conversation
@jehiah: anything required to merge this? |
Pinging @jehiah ... |
The last commit in the master is Nov 18, 2016. Probably it's just about the time to fork the project? :) |
@akobyakov: I suspect that no one wants to be the maintainer. Maybe trying pinging @bitly on Twitter? |
I think that if someone stepped-up with a fork, which incorporate this PR as well as the websocket support one, and was reasonably well tested and maintained, it could gain traction and then get a link from this repo's README. I haven't worked at Bitly in a few years, so take that with a grain of salt. I'm pretty sure the bitly twitter account is the wrong contact for this issue. I'd instead ping @SeanOC and @markrechler |
@jehiah you seem to be active again -- is there any interest in merging this? |
Yes! sorry for the moving target on master. Can you rebase this? Also It's worth mentioning that I'm not personally using this configuration, so it'd be really really really nice to get a setup on travis that exercises this config. Would you be interested in trying to add some sort of tests in this PR? |
This is enhancement of #173 to use "Auth Request" consistently in the command-line option, configuration file and response headers. It always sets the X-Auth-Request-User response header and if the email is available, sets X-Auth-Request-Email as well.
This is useful in Nginx auth_request mode, if a 401 handler is configured to redirect to the sign-in page. As the request URL does not reflect the actual URL, the value is taken from the header "X-Auth-Request-Redirect" instead. Based on #247
@jehiah: rebased on top of latest master. Not sure if you noticed the test |
@ashkulz I think i'm just musing about getting an end-to-end test running via jenkins that includes actually requesting through nginx. That can happen later though. Thanks for these improvements |
Not sure if that can run on Travis CI. BTW, the merge build failed -- maybe a flaky test?
Also, any ETA for a 2.2 release? 😄 |
soon. I am working on some more complete validation in this build, but I think it's already got enough fixes/changes to warrant a release, even if there are plenty more queued up to do another release in a month or two. |
This supersedes #173 and #247, with the following changes:
--set-xauthrequest
which sets response headers for use in auth_request mode (analogous to theX-Forwarded-User
andX-Forwarded-Email
headers in normal mode).X-Auth-Request-Redirect
as the request URL doesn't correspond to the URL to redirect to in auth_request mode