I'm just futzing with mod_auth_sspi on my local desktop and, for the most part, everything works as expected. I'm working with Ruby on Rails, so I've setup a ProxyPass through port 3000 (I'm using WEBrick, a simple Ruby web server), and that works fine for the most part.
The problem I'm having is that a 401 doesn't seem to get passed back through the proxy. I just get an error page. I can see the error in the Apache log file. But it never gets back to WEBrick.
What I want is to be able to handle the 401 within the Rails, but at the moment it never gets the chance to. Basically I want to intercept the 401 and simply redirect them to the login page.
Hi,
I'm just futzing with mod_auth_sspi on my local desktop and, for the most part, everything works as expected. I'm working with Ruby on Rails, so I've setup a ProxyPass through port 3000 (I'm using WEBrick, a simple Ruby web server), and that works fine for the most part.
The problem I'm having is that a 401 doesn't seem to get passed back through the proxy. I just get an error page. I can see the error in the Apache log file. But it never gets back to WEBrick.
What I want is to be able to handle the 401 within the Rails, but at the moment it never gets the chance to. Basically I want to intercept the 401 and simply redirect them to the login page.
I have a pretty standard setup I think:
Is there some Apache directive I need to add to get the 401 to proxy back?
Thanks,
Dan
Typo in my post. The DocumentRoot and Directory actually do match in reality. SF doesn't support editing posts apparently.