See: http://code.google.com/p/modwsgi/wiki/AccessControlMechanisms#HTTP_User_Authentication
On Tuesday, December 21, 2010 6:25:34 AM UTC+11, strattonbrazil wrote: > > Reading more through the docs, I believe I have redirection working by > setting server.webpath to what my SCRIPT_NAME is and setting my > SCRIPT_NAME to an empty string, but now it's getting hung up on the > Turbogears authentication. > > auth.getHttpAuth() > > The login pops up in my browser, but it no longer accepts my username/ > password. Do I need to now use mod_wsgi to authenticate now? Or do I > need that configuration file to make sure TG knows how to > authenticate? > > On Dec 20, 9:06 am, strattonbrazil <[email protected]> wrote: > > I'm trying to get a TG app using TG 1.0.5 running on mod_wsgi. I've > > been following this guide, > > > > http://code.google.com/p/modwsgi/wiki/IntegrationWithTurboGears > > > > and have had some success getting the default() method called, but > > only the default() method and not the other exposed methods like > > index(). Right now I'm not pointing to any configuration file as I > > didn't have one before, but on the cherrypy mailing list, where I > > originally went, they suggested I need one to set the root mount > > point. I also read somewhere that TG 1 doesn't honor SCRIPT_NAME, but > > it also has to be set to an empty string or something? > > > > turbogears.update_config(configfile="dev.cfg", > > modulename="mysite.config") > > > > Basically, I have the above line commented out and I need to know: > > 1) Is this config file my problem? If so, what specifically do I need > > in the file to get the dispatcher working? > > 2) Do I need to do anything with SCRIPT_NAME or can I just ignore > > that? -- You received this message because you are subscribed to the Google Groups "TurboGears" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/turbogears?hl=en.
