On 16 June 2010 09:13, Jason Garber <[email protected]> wrote: > Have you considered a simple mod_rewrite rule? > RewriteEngine on > RewriteCond ${REQUEST_URI} !=/login > RewriteRule ^/login$ /login [NC,PT,L] > > See http://httpd.apache.org/docs/2.2/mod/mod_rewrite.html -- search for > [PT] > Or perhaps even better, use a redirect: > RewriteEngine on > RewriteCond ${REQUEST_URI} !=/login > RewriteRule ^/login$ /login [NC,R,L] > > That insulates your application from this issue, and maintains a consistent > URL even if people *get* there using /LoGiN
You may have to be a bit careful from memory as REQUEST_URI hasn't been decoded. Would pick up the bulk of cases though and only where user did something stupid wouldn't it work. :-) Graham > -JG > > On Mon, Jun 14, 2010 at 3:23 PM, viper <[email protected]> wrote: >> >> This is under my virtual host and works great: >> WSGIScriptAlias /login /var/wsgi/login.wsgi >> >> http://mysite.com/login <-- works. >> >> How do I make it so "login" can be case in-sensitive? Login, LOGIN, >> LoGiN ? >> >> I placed the following in my WSGI.CONF file (apache2) which gets >> imported into apache2.conf on server restart along with the modules: >> >> WSGICaseSensitivity Off >> >> And restarted my server. However, not working... /login <-- works, / >> Login <-- not working >> >> Anything else I need to do? -- You received this message because you are subscribed to the Google Groups "modwsgi" 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/modwsgi?hl=en.
